OBSDOCS-1629: Fix

[max-cx]

Version(s): main, 4.19

Issue: https://issues.redhat.com/browse/OBSDOCS-1629

Link to docs preview:

• https://93526--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/distr_tracing/distr-tracing-rn
• https://93526--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-rn

QE review: N/A

Additional information: Fix for #92944

[openshift-ci-robot]

@max-cx: This pull request references OBSDOCS-1629 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

In response to this:

Version(s):

Issue:

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@max-cx: This pull request references OBSDOCS-1629 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

In response to this:

Version(s): main, 4.19

Issue: https://issues.redhat.com/browse/OBSDOCS-1629

Link to docs preview:

QE review: N/A

Additional information: Fix for #92944

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[ocpdocs-previewbot]

🤖 Tue May 27 22:59:18 - Prow CI generated the docs preview:
https://93526--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

[openshift-ci-robot]

@max-cx: This pull request references OBSDOCS-1629 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

In response to this:

Version(s): main, 4.19

Issue: https://issues.redhat.com/browse/OBSDOCS-1629

Link to docs preview:

• https://93526--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/distr_tracing/distr-tracing-rn
• https://93526--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-rn

QE review: N/A

Additional information: Fix for #92944

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[max-cx]

/label peer-review needed

[max-cx]

/label peer-review-needed

[openshift-ci]

@max-cx: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci]

@max-cx: Those labels are not set on the issue: merge-review-needed

In response to this:

/remove-label merge-review-needed

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[GroceryBoyJr]

/remove-label merge-review-needed
/label peer-review-in-progress
/remove-label peer-review-needed
/assign GroceryBoyJr

[GroceryBoyJr]

LGTM

[GroceryBoyJr]

/label peer-review-done
/remove-label peer-review-in-progress
/unassign GroceryBoyJr

[GroceryBoyJr]

@max-cx I had to remove the merge-review-needed, per our process, and didn't add it back in (per our process). I don't mean to cause inconvenience! Please, just add the label back in when you are ready.

[max-cx]

/label merge-review-needed

[michaelryanpeter]

/label merge-review-in-progress

[michaelryanpeter]

LGTM

There has been some debate as to whether or not to have the include statement above the h1 for assemblies that don't need it (Slack thread). Currently, our guidelines state to use it when you need it (first assembly in a section if that assembly has an attribute). The rule remains in place due to a bug in the asciidoc VS code extension.

Since this is valid asciidoc, isn't customer-facing, and has limited impact, I don't think it is worth blocking a merge. I only mention it for context/awareness. I'm not sure if it is worth following up in another PR unless something breaks. Please double check after everything is published on d.r.c.

[michaelryanpeter]

/cherrypick enterprise-4.19

[openshift-cherrypick-robot]

@michaelryanpeter: new pull request created: #93963

In response to this:

/cherrypick enterprise-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.