Skip to content

Comments

[enterprise-4.21] OSDOCS-16848#106783

Merged
JoeAldinger merged 1 commit intoopenshift:enterprise-4.21from
JoeAldinger:OSDOCS-16848-4.21
Feb 17, 2026
Merged

[enterprise-4.21] OSDOCS-16848#106783
JoeAldinger merged 1 commit intoopenshift:enterprise-4.21from
JoeAldinger:OSDOCS-16848-4.21

Conversation

@JoeAldinger
Copy link
Contributor

@JoeAldinger JoeAldinger commented Feb 17, 2026

Version(s):

Issue:
https://issues.redhat.com/browse/OSDOCS-16848

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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

openshift-ci-robot commented Feb 17, 2026

@JoeAldinger: This pull request references OSDOCS-10818 which is a valid jira issue.

Details

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 openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 17, 2026
@JoeAldinger
Copy link
Contributor Author

#106087
commit Id: 4a21e0f

@JoeAldinger JoeAldinger changed the title OSDOCS-10818: Introducing oc adm upgrade status (tech preview)4.2 [enterprise-4.21] OSDOCS-16848 Feb 17, 2026
@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 17, 2026
@openshift-ci-robot
Copy link

@JoeAldinger: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

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.

= Checking the status of the DNS Operator

[role="_abstract"]
You can check the DNS Operator deployment and cluster operator status. The DNS Operator is deployed during installation with a `Deployment` object.
Copy link
Collaborator

Choose a reason for hiding this comment

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

🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.

@openshift-ci
Copy link

openshift-ci bot commented Feb 17, 2026

@JoeAldinger: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@JoeAldinger JoeAldinger merged commit 438bdac into openshift:enterprise-4.21 Feb 17, 2026
2 checks passed
@JoeAldinger
Copy link
Contributor Author

/cherrypick enterprise-4.20

@openshift-cherrypick-robot

@JoeAldinger: new pull request created: #106791

Details

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.

@JoeAldinger
Copy link
Contributor Author

/cherrypick enterprise-4.19

@JoeAldinger
Copy link
Contributor Author

/cherrypick enterprise-4.18

@JoeAldinger
Copy link
Contributor Author

/cherrypick enterprise-4.17

@openshift-cherrypick-robot

@JoeAldinger: new pull request created: #106795

Details

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

@JoeAldinger: #106783 failed to apply on top of branch "enterprise-4.18":

Applying: NOP-7
Using index info to reconstruct a base tree...
M	modules/k8s-nmstate-deploying-nmstate-CLI.adoc
M	modules/k8s-nmstate-installing-the-kubernetes-nmstate-operator.adoc
M	modules/k8s-nmstate-uninstall-operator.adoc
M	modules/nw-dns-forward.adoc
M	modules/nw-dns-view.adoc
M	modules/nw-infw-operator-config-object.adoc
M	modules/nw-infw-operator-cr.adoc
M	modules/nw-infw-operator-installing-cli.adoc
M	modules/nw-infw-operator-installing-console.adoc
M	modules/viewing-stats-collected-kubernetes-nmtate-op.adoc
M	networking/networking_operators/dns-operator.adoc
M	networking/networking_operators/ingress-node-firewall-operator.adoc
Falling back to patching base and 3-way merge...
Auto-merging networking/networking_operators/ingress-node-firewall-operator.adoc
Auto-merging networking/networking_operators/dns-operator.adoc
Auto-merging modules/viewing-stats-collected-kubernetes-nmtate-op.adoc
Auto-merging modules/nw-infw-operator-installing-console.adoc
Auto-merging modules/nw-infw-operator-installing-cli.adoc
Auto-merging modules/nw-infw-operator-cr.adoc
Auto-merging modules/nw-infw-operator-config-object.adoc
CONFLICT (content): Merge conflict in modules/nw-infw-operator-config-object.adoc
Auto-merging modules/nw-dns-view.adoc
Auto-merging modules/nw-dns-forward.adoc
CONFLICT (content): Merge conflict in modules/nw-dns-forward.adoc
Auto-merging modules/k8s-nmstate-uninstall-operator.adoc
CONFLICT (content): Merge conflict in modules/k8s-nmstate-uninstall-operator.adoc
Auto-merging modules/k8s-nmstate-installing-the-kubernetes-nmstate-operator.adoc
Auto-merging 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 set advice.mergeConflict false"
Patch failed at 0001 NOP-7

Details

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

@JoeAldinger: #106783 failed to apply on top of branch "enterprise-4.17":

Applying: NOP-7
Using index info to reconstruct a base tree...
M	modules/k8s-nmstate-deploying-nmstate-CLI.adoc
M	modules/k8s-nmstate-installing-the-kubernetes-nmstate-operator.adoc
M	modules/k8s-nmstate-uninstall-operator.adoc
M	modules/nw-controlling-dns-pod-placement.adoc
M	modules/nw-dns-forward.adoc
M	modules/nw-infw-operator-config-object.adoc
M	modules/nw-infw-operator-cr.adoc
M	modules/nw-infw-operator-installing-cli.adoc
M	modules/nw-infw-operator-installing-console.adoc
M	modules/viewing-stats-collected-kubernetes-nmtate-op.adoc
M	networking/networking_operators/dns-operator.adoc
M	networking/networking_operators/ingress-node-firewall-operator.adoc
Falling back to patching base and 3-way merge...
Auto-merging networking/networking_operators/ingress-node-firewall-operator.adoc
Auto-merging networking/networking_operators/dns-operator.adoc
Auto-merging modules/viewing-stats-collected-kubernetes-nmtate-op.adoc
Auto-merging modules/nw-infw-operator-installing-console.adoc
Auto-merging modules/nw-infw-operator-installing-cli.adoc
Auto-merging modules/nw-infw-operator-cr.adoc
Auto-merging modules/nw-infw-operator-config-object.adoc
CONFLICT (content): Merge conflict in modules/nw-infw-operator-config-object.adoc
Auto-merging modules/nw-dns-forward.adoc
CONFLICT (content): Merge conflict in modules/nw-dns-forward.adoc
Auto-merging modules/nw-controlling-dns-pod-placement.adoc
CONFLICT (content): Merge conflict in modules/nw-controlling-dns-pod-placement.adoc
Auto-merging modules/k8s-nmstate-uninstall-operator.adoc
CONFLICT (content): Merge conflict in modules/k8s-nmstate-uninstall-operator.adoc
Auto-merging modules/k8s-nmstate-installing-the-kubernetes-nmstate-operator.adoc
Auto-merging 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 set advice.mergeConflict false"
Patch failed at 0001 NOP-7

Details

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

size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants