Skip to content

Conversation

eromanova97
Copy link
Contributor

@eromanova97 eromanova97 commented Sep 17, 2025

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 17, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 17, 2025

@eromanova97: This pull request references OBSDOCS-2230 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 bug to target the "4.21.0" version, but no target version was set.

In response to this:

Version(s): 4.18 +

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

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 openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 17, 2025
Copy link

openshift-ci bot commented Sep 17, 2025

@eromanova97: 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.

@juzhao
Copy link

juzhao commented Sep 17, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 17, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 17, 2025

@eromanova97: This pull request references OBSDOCS-2230 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 bug to target the "4.21.0" version, but no target version was set.

In response to this:

Version(s): 4.18 +

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

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
Copy link

openshift-ci-robot commented Sep 17, 2025

@eromanova97: This pull request references OBSDOCS-2230 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 bug to target the "4.21.0" version, but no target version was set.

In response to this:

Version(s): 4.18 +

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

Link to docs preview: https://99181--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/monitoring/about-ocp-monitoring/monitoring-stack-architecture.html#monitoring-common-terms_monitoring-stack-architecture

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.

@theashiot
Copy link
Contributor

LGTM @eromanova97

@eromanova97 eromanova97 merged commit ffa9f7a into openshift:main Sep 18, 2025
2 checks passed
@eromanova97 eromanova97 added this to the Continuous Release milestone Sep 18, 2025
@eromanova97
Copy link
Contributor Author

/cherrypick enterprise-4.20

@eromanova97
Copy link
Contributor Author

/cherrypick enterprise-4.19

@eromanova97
Copy link
Contributor Author

/cherrypick enterprise-4.18

@eromanova97
Copy link
Contributor Author

/cherrypick monitoring-docs-main

@openshift-cherrypick-robot

@eromanova97: new pull request created: #99313

In response to this:

/cherrypick enterprise-4.20

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.

@openshift-cherrypick-robot

@eromanova97: new pull request created: #99314

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.

@openshift-cherrypick-robot

@eromanova97: new pull request created: #99315

In response to this:

/cherrypick enterprise-4.18

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.

@openshift-cherrypick-robot

@eromanova97: #99181 failed to apply on top of branch "monitoring-docs-main":

Applying: OBSDOCS-2230: Fluentd is incorrectly referred in RHOCP 4.18+ monitoring docs
Using index info to reconstruct a base tree...
M	modules/monitoring-common-terms.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/monitoring-common-terms.adoc
CONFLICT (content): Merge conflict in modules/monitoring-common-terms.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OBSDOCS-2230: Fluentd is incorrectly referred in RHOCP 4.18+ monitoring docs

In response to this:

/cherrypick monitoring-docs-main

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.18 branch/enterprise-4.19 branch/enterprise-4.20 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants