Skip to content

Conversation

@dfitzmau
Copy link
Contributor

@dfitzmau dfitzmau commented Oct 1, 2025

Version(s):
4.16+

Issue:
OSDOCS-16361

Link to docs preview:

  • SME has approved this change (Enrique).
  • QE has approved this change (Meina Li).

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

openshift-ci-robot commented Oct 1, 2025

@dfitzmau: This pull request references OSDOCS-16361 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 story to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20" instead.

In response to this:

Version(s):

Issue:
OSDOCS-16361

Link to docs preview:

  • SME has approved this change.
  • QE has approved this change.

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/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Oct 1, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Oct 1, 2025

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 1, 2025

@dfitzmau: This pull request references OSDOCS-16361 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 story to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20" instead.

In response to this:

Version(s):
4.12+

Issue:
OSDOCS-16361

Link to docs preview:

  • SME has approved this change.
  • QE has approved this change.

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 Oct 1, 2025

@dfitzmau: This pull request references OSDOCS-16361 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 story to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20" instead.

In response to this:

Version(s):
4.12+

Issue:
OSDOCS-16361

Link to docs preview:

  • SME has approved this change.
  • QE has approved this change.

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.

@dfitzmau
Copy link
Contributor Author

dfitzmau commented Oct 2, 2025

/retest

@openshift-ci
Copy link

openshift-ci bot commented Oct 2, 2025

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

Copy link

@qinqon qinqon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

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

openshift-ci-robot commented Oct 2, 2025

@dfitzmau: This pull request references OSDOCS-16361 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 story to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20" instead.

In response to this:

Version(s):
4.12+

Issue:
OSDOCS-16361

Link to docs preview:

  • SME has approved this change (Enrique).
  • QE has approved this change.

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 Oct 2, 2025

@dfitzmau: This pull request references OSDOCS-16361 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 story to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20" instead.

In response to this:

Version(s):
4.12+

Issue:
OSDOCS-16361

Link to docs preview:

  • SME has approved this change (Enrique).
  • QE has approved this change (Meina Li).

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.

@Meina-rh
Copy link

Meina-rh commented Oct 9, 2025

/lgtm

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 9, 2025

@dfitzmau: This pull request references OSDOCS-16361 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 story to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20" instead.

In response to this:

Version(s):
4.12+

Issue:
OSDOCS-16361

Link to docs preview:

  • SME has approved this change (Enrique).
  • QE has approved this change (Meina Li).

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.

@dfitzmau dfitzmau added the merge-review-needed Signifies that the merge review team needs to review this PR label Oct 9, 2025
@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.13

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.14

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.15

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.16

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.17

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.18

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.19

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.20

@openshift-cherrypick-robot

@xenolinux: #99905 failed to apply on top of branch "enterprise-4.12":

Applying: OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc
Using index info to reconstruct a base tree...
M	modules/k8s-nmstate-deploying-nmstate-CLI.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/k8s-nmstate-deploying-nmstate-CLI.adoc
CONFLICT (content): Merge conflict in modules/k8s-nmstate-deploying-nmstate-CLI.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 OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc

In response to this:

/cherrypick enterprise-4.12

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

@xenolinux: #99905 failed to apply on top of branch "enterprise-4.13":

Applying: OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc
Using index info to reconstruct a base tree...
M	modules/k8s-nmstate-deploying-nmstate-CLI.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/k8s-nmstate-deploying-nmstate-CLI.adoc
CONFLICT (content): Merge conflict in modules/k8s-nmstate-deploying-nmstate-CLI.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 OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc

In response to this:

/cherrypick enterprise-4.13

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

@xenolinux: #99905 failed to apply on top of branch "enterprise-4.14":

Applying: OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc
Using index info to reconstruct a base tree...
M	modules/k8s-nmstate-deploying-nmstate-CLI.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/k8s-nmstate-deploying-nmstate-CLI.adoc
CONFLICT (content): Merge conflict in modules/k8s-nmstate-deploying-nmstate-CLI.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 OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc

In response to this:

/cherrypick enterprise-4.14

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

@xenolinux: #99905 failed to apply on top of branch "enterprise-4.15":

Applying: OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc
Using index info to reconstruct a base tree...
M	modules/k8s-nmstate-deploying-nmstate-CLI.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/k8s-nmstate-deploying-nmstate-CLI.adoc
CONFLICT (content): Merge conflict in modules/k8s-nmstate-deploying-nmstate-CLI.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 OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc

In response to this:

/cherrypick enterprise-4.15

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

@xenolinux: #99905 failed to apply on top of branch "enterprise-4.17":

Applying: OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc
Using index info to reconstruct a base tree...
M	modules/k8s-nmstate-deploying-nmstate-CLI.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/k8s-nmstate-deploying-nmstate-CLI.adoc
CONFLICT (content): Merge conflict in modules/k8s-nmstate-deploying-nmstate-CLI.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 OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc

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

@xenolinux: new pull request created: #100261

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

@xenolinux: #99905 failed to apply on top of branch "enterprise-4.18":

Applying: OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc
Using index info to reconstruct a base tree...
M	modules/k8s-nmstate-deploying-nmstate-CLI.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/k8s-nmstate-deploying-nmstate-CLI.adoc
CONFLICT (content): Merge conflict in modules/k8s-nmstate-deploying-nmstate-CLI.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 OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc

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

@xenolinux: new pull request created: #100262

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

@xenolinux: new pull request created: #100263

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.

@dfitzmau
Copy link
Contributor Author

dfitzmau commented Oct 9, 2025

/cherrypick enterprise-4.18

@dfitzmau
Copy link
Contributor Author

dfitzmau commented Oct 9, 2025

/cherrypick enterprise-4.17

@openshift-cherrypick-robot

@dfitzmau: #99905 failed to apply on top of branch "enterprise-4.18":

Applying: OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc
Using index info to reconstruct a base tree...
M	modules/k8s-nmstate-deploying-nmstate-CLI.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/k8s-nmstate-deploying-nmstate-CLI.adoc
CONFLICT (content): Merge conflict in modules/k8s-nmstate-deploying-nmstate-CLI.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 OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc

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

@dfitzmau: #99905 failed to apply on top of branch "enterprise-4.17":

Applying: OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc
Using index info to reconstruct a base tree...
M	modules/k8s-nmstate-deploying-nmstate-CLI.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/k8s-nmstate-deploying-nmstate-CLI.adoc
CONFLICT (content): Merge conflict in modules/k8s-nmstate-deploying-nmstate-CLI.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 OSDOCS-16361: Added new verification command to k8s-nmstate-deploying-nmstate-CLI.adoc

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.

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. lgtm Indicates that a PR is ready to be merged. 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.

7 participants