Skip to content

Conversation

max-cx
Copy link
Contributor

@max-cx max-cx commented Mar 5, 2024

Cherry-picking commit 34205d3 with the necessary manual edit (using the opportunity to manually solve merge conflicts) to remove the Power Monitoring content, which is not present in 4.13.

Version(s):

4.13

Issue:

https://issues.redhat.com/browse/OBSDOCS-886
https://issues.redhat.com/browse/OBSDOCS-887
https://issues.redhat.com/browse/OBSDOCS-689

Link to docs preview:

https://72630--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/

QE review:

  • N/A

Additional information:

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 5, 2024

@max-cx: This pull request references OBSDOCS-689 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.16.0" version, but no target version was set.

In response to this:

Cherry-picking commit 34205d3 with the necessary manual edit (using the opportunity to manually solve merge conflicts) to remove the Power Monitoring content, which is not present in 4.13.

Version(s):

4.13

Issue:

https://issues.redhat.com/browse/OBSDOCS-886
https://issues.redhat.com/browse/OBSDOCS-887
https://issues.redhat.com/browse/OBSDOCS-689

Link to docs preview:

QE review:

  • N/A

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 5, 2024
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 5, 2024
@max-cx max-cx changed the base branch from main to enterprise-4.13 March 5, 2024 15:19
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 5, 2024

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

In response to this:

Cherry-picking commit 34205d3 with the necessary manual edit (using the opportunity to manually solve merge conflicts) to remove the Power Monitoring content, which is not present in 4.13.

Version(s):

4.13

Issue:

https://issues.redhat.com/browse/OBSDOCS-886
https://issues.redhat.com/browse/OBSDOCS-887
https://issues.redhat.com/browse/OBSDOCS-689

Link to docs preview:

QE review:

  • N/A

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 openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 5, 2024
@max-cx
Copy link
Contributor Author

max-cx commented Mar 5, 2024

/retest

@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Mar 5, 2024

🤖 Wed Mar 13 18:53:08 - Prow CI generated the docs preview:
https://72630--ocpdocs-pr.netlify.app

@openshift-ci-robot
Copy link

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

In response to this:

Cherry-picking commit 34205d3 with the necessary manual edit (using the opportunity to manually solve merge conflicts) to remove the Power Monitoring content, which is not present in 4.13.

Version(s):

4.13

Issue:

https://issues.redhat.com/browse/OBSDOCS-886
https://issues.redhat.com/browse/OBSDOCS-887
https://issues.redhat.com/browse/OBSDOCS-689

Link to docs preview:

https://72630--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/

QE review:

  • N/A

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-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 7, 2024
@max-cx
Copy link
Contributor Author

max-cx commented Mar 13, 2024

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Mar 13, 2024
@adellape adellape self-assigned this Mar 13, 2024
@adellape adellape added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Mar 13, 2024
@max-cx
Copy link
Contributor Author

max-cx commented Mar 13, 2024

/label distributed-tracing

@openshift-ci openshift-ci bot added the distributed-tracing Label for all Distributed Tracing PRs label Mar 13, 2024
 Cherry-picking commit 34205d3.
	modified:   _attributes/common-attributes.adoc
	modified:   _topic_maps/_topic_map.yml
	new file:   observability/_attributes
	new file:   observability/hugeBook.flag
	new file:   observability/images
	new file:   observability/index.adoc
	new file:   observability/modules
	new file:   observability/snippets
Copy link

openshift-ci bot commented Mar 13, 2024

@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/test-infra repository. I understand the commands that are listed here.

@adellape adellape merged commit 56e891c into openshift:enterprise-4.13 Mar 13, 2024
@adellape adellape added peer-review-done Signifies that the peer review team has reviewed this PR and removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels Mar 13, 2024
@adellape adellape added this to the Continuous Release milestone Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.13 distributed-tracing Label for all Distributed Tracing PRs jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. peer-review-done Signifies that the peer review team has reviewed this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants