Skip to content

Conversation

@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 17, 2025

@eromanova97: This pull request references OBSDOCS-2299 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.16 +

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

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

openshift-ci-robot commented Sep 17, 2025

@eromanova97: This pull request references OBSDOCS-2299 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.16 +

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

Link to docs preview:

QE review: n/a

Additional information:
See:
image

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
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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 17, 2025

@eromanova97: This pull request references OBSDOCS-2299 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.16 +

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

Link to docs preview:

QE review: n/a

Additional information:
See:
image

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 added this to the Continuous Release milestone Sep 17, 2025
@eromanova97 eromanova97 merged commit 256955e into openshift:main Sep 17, 2025
2 checks passed
@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 enterprise-4.17

@eromanova97
Copy link
Contributor Author

/cherrypick enterprise-4.16

@eromanova97
Copy link
Contributor Author

/cherrypick monitoring-docs-main

@openshift-cherrypick-robot

@eromanova97: new pull request created: #99190

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: #99191

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: #99183 failed to apply on top of branch "enterprise-4.18":

Applying: OBSDOCS-2299: doc mismatches dev console
Using index info to reconstruct a base tree...
M	modules/monitoring-reviewing-monitoring-dashboards-admin.adoc
M	modules/monitoring-reviewing-monitoring-dashboards-developer.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/monitoring-reviewing-monitoring-dashboards-developer.adoc
CONFLICT (content): Merge conflict in modules/monitoring-reviewing-monitoring-dashboards-developer.adoc
Auto-merging modules/monitoring-reviewing-monitoring-dashboards-admin.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-2299: doc mismatches dev console

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: #99183 failed to apply on top of branch "enterprise-4.17":

Applying: OBSDOCS-2299: doc mismatches dev console
Using index info to reconstruct a base tree...
M	modules/monitoring-reviewing-monitoring-dashboards-admin.adoc
M	modules/monitoring-reviewing-monitoring-dashboards-developer.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/monitoring-reviewing-monitoring-dashboards-developer.adoc
CONFLICT (content): Merge conflict in modules/monitoring-reviewing-monitoring-dashboards-developer.adoc
Auto-merging modules/monitoring-reviewing-monitoring-dashboards-admin.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-2299: doc mismatches dev console

In response to this:

/cherrypick enterprise-4.17

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: #99183 failed to apply on top of branch "enterprise-4.16":

Applying: OBSDOCS-2299: doc mismatches dev console
Using index info to reconstruct a base tree...
M	modules/monitoring-reviewing-monitoring-dashboards-admin.adoc
M	modules/monitoring-reviewing-monitoring-dashboards-developer.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/monitoring-reviewing-monitoring-dashboards-developer.adoc
CONFLICT (content): Merge conflict in modules/monitoring-reviewing-monitoring-dashboards-developer.adoc
Auto-merging modules/monitoring-reviewing-monitoring-dashboards-admin.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-2299: doc mismatches dev console

In response to this:

/cherrypick enterprise-4.16

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: #99192

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.

@eromanova97
Copy link
Contributor Author

/cherrypick enterprise-4.18

@openshift-cherrypick-robot

@eromanova97: #99183 failed to apply on top of branch "enterprise-4.18":

Applying: OBSDOCS-2299: doc mismatches dev console
Using index info to reconstruct a base tree...
M	modules/monitoring-reviewing-monitoring-dashboards-admin.adoc
M	modules/monitoring-reviewing-monitoring-dashboards-developer.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/monitoring-reviewing-monitoring-dashboards-developer.adoc
CONFLICT (content): Merge conflict in modules/monitoring-reviewing-monitoring-dashboards-developer.adoc
Auto-merging modules/monitoring-reviewing-monitoring-dashboards-admin.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-2299: doc mismatches dev console

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.

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

Labels

branch/enterprise-4.16 branch/enterprise-4.17 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. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants