Skip to content

Conversation

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

openshift-ci-robot commented Aug 6, 2025

@sbeskin-redhat: This pull request references CNV-55995 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 the "4.20.0" version, but no target version was set.

In response to this:

Resolves: https://issues.redhat.com/browse/CNV-55995

CNV 4.20
OCP 4.20

Preview:

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 Aug 6, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Aug 6, 2025

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 6, 2025

@sbeskin-redhat: This pull request references CNV-55995 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 the "4.20.0" version, but no target version was set.

In response to this:

Resolves: https://issues.redhat.com/browse/CNV-55995

CNV 4.20
OCP 4.20

Preview:
https://97234--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.html#virt-viewing-network-state-of-node-console_k8s-nmstate-updating-node-network-config
https://97234--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.html#virt-create-node-network-config-console_k8s-nmstate-updating-node-network-config

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 Aug 6, 2025

@sbeskin-redhat: This pull request references CNV-55995 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 the "4.20.0" version, but no target version was set.

In response to this:

Resolves: https://issues.redhat.com/browse/CNV-55995

CNV 4.19+
OCP 4.19+

Preview:
https://97234--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.html#virt-viewing-network-state-of-node-console_k8s-nmstate-updating-node-network-config
https://97234--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.html#virt-create-node-network-config-console_k8s-nmstate-updating-node-network-config

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.

@lkladnit
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 11, 2025
@ctomasko
Copy link

@sbeskin-redhat all approvals received. This PR is ready to merge.

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 21, 2025
@ousleyp ousleyp added this to the Continuous Release milestone Aug 21, 2025
Copy link
Member

@ousleyp ousleyp left a comment

Choose a reason for hiding this comment

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

This is looking pretty good, but there are a few things that must be fixed before you request a merge review. Thanks @sbeskin-redhat! (Ah! And don't forget to squash to one commit.)

.. Enter the name of the interface in *Interface name* field.

.. Select the network state from *Network state* dropdown. The default selected value is *Up*.
.. Select the required network state in the *Network state* part of the section. The default selected state is *Up*.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
.. Select the required network state in the *Network state* part of the section. The default selected state is *Up*.
.. Select the required network state in the *Network state* list. The default selected state is *Up*.

If it's what we would normally call a "dropdown menu," we use "list"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@ousleyp This is not a dropdown menu and not a list. It's just several radio buttons, and each one selects a state. Maybe just "Select the required network state." would be enough.

.. Select the required network state in the *Network state* part of the section. The default selected state is *Up*.

.. Select the type of interface from *Type* dropdown. The available values are *Bridge*, *Bonding*, and *Ethernet*. The default selected value is *Bridge*.
.. Select the type of interface in the *Type* part of the section. The available types are *Bridge*, *Bonding*, and *Ethernet*. The default selected value is *Bridge*.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
.. Select the type of interface in the *Type* part of the section. The available types are *Bridge*, *Bonding*, and *Ethernet*. The default selected value is *Bridge*.
.. Select the type of interface in the *Type* list. The available types are *Bridge*, *Bonding*, and *Ethernet*. The default selected value is *Bridge*.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@ousleyp Same as above.

@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Aug 25, 2025
@sbeskin-redhat sbeskin-redhat force-pushed the CNV_55995_Host_network_configuration_visualization branch 2 times, most recently from da0b423 to 5f523dd Compare August 25, 2025 19:36
@sbeskin-redhat
Copy link
Contributor Author

@ousleyp Thank you! I made the changes. Please take a look. If it's OK, could you merge it?

@ousleyp
Copy link
Member

ousleyp commented Aug 25, 2025

@ousleyp Thank you! I made the changes. Please take a look. If it's OK, could you merge it?

Hi @sbeskin-redhat, please remove backup_and_restore/build/en-US/master.xml from your PR before requesting merge review. Looks like that was accidentally added somehow. :)

@sbeskin-redhat sbeskin-redhat force-pushed the CNV_55995_Host_network_configuration_visualization branch from 43493bd to 9d48ac2 Compare August 26, 2025 18:34
@sbeskin-redhat
Copy link
Contributor Author

@ousleyp Done

Copy link
Member

@ousleyp ousleyp left a comment

Choose a reason for hiding this comment

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

A few nits, but otherwise it's looking good.


.Procedure
. Navigate to *Networking**Node Network Configuration*.
. In the upper-right corner of the page, click the *List* icon.
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@ousleyp So how should I point the user to that tiny icon tucked away in, well... the upper-right corner?

@lkladnit
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 27, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 27, 2025
Copy link

openshift-ci bot commented Aug 27, 2025

New changes are detected. LGTM label has been removed.

@sbeskin-redhat sbeskin-redhat force-pushed the CNV_55995_Host_network_configuration_visualization branch from 6526d7c to c6142d2 Compare August 27, 2025 18:05
Copy link

openshift-ci bot commented Aug 27, 2025

@sbeskin-redhat: 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.

@sbeskin-redhat
Copy link
Contributor Author

@ousleyp I made the changes. Can we merge the PR now?

@ousleyp ousleyp merged commit eb519a9 into openshift:main Aug 28, 2025
2 checks passed
@ousleyp
Copy link
Member

ousleyp commented Aug 28, 2025

/cherrypick enterprise-4.20

@ousleyp
Copy link
Member

ousleyp commented Aug 28, 2025

/cherrypick enterprise-4.19

@openshift-cherrypick-robot

@ousleyp: #97234 failed to apply on top of branch "enterprise-4.20":

Applying: CNV-55995
.git/rebase-apply/patch:122: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc
Falling back to patching base and 3-way merge...
Auto-merging networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc
CONFLICT (content): Merge conflict in networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc
Removing modules/virt-viewing-network-state-of-node-console.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 CNV-55995

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

@ousleyp: #97234 failed to apply on top of branch "enterprise-4.19":

Applying: CNV-55995
.git/rebase-apply/patch:122: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc
Falling back to patching base and 3-way merge...
Auto-merging networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc
CONFLICT (content): Merge conflict in networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc
Removing modules/virt-viewing-network-state-of-node-console.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 CNV-55995

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.

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

Labels

branch/enterprise-4.19 branch/enterprise-4.20 CNV Label for all CNV PRs jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. 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.

8 participants