OPNET-681,OCPBUGS-57484: Support migration to NMState #5064

cybertron · 2025-05-19T20:57:57Z

This PR adds logic to handle two migration paths to NMState: one from an existing OVNK cluster using configure-ovs, and one from OpenShift SDN directly to NMState without ever using configure-ovs.

In the former case, we need to clean up the left over remnants of configure-ovs's br-ex configuration. In the latter we need to clean up br0, which would otherwise have been done by configure-ovs.

- What I did

- How to verify it

- Description for the changelog

openshift-ci-robot · 2025-05-19T20:58:01Z

@cybertron: This pull request references OPNET-681 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:

Even though configure-ovs uses in-memory profiles to ensure we are starting with a clean slate on each boot, the OVS database may still have leftover artifacts in it. This causes issues if you try to switch to using NMState to manage br-ex because the entries conflict with what NMState does.

This patch simply adds a call to delete br-ex from the ovsdb if it exists when we apply an NMState configuration.

- What I did

- How to verify it

- Description for the changelog

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.

cybertron · 2025-05-22T19:47:47Z

/retest-required

Image pull failed

yuqi-zhang · 2025-05-22T20:31:41Z

/retest-required

cybertron · 2025-06-17T17:24:20Z

/cc @mkowalski @emy

This has some overlap with the disruptive change work because in that case br-ex will already exist too. I think it should be fine since we'll be reconfiguring it anyway, but it will be something to test.

templates/common/_base/files/nmstate-configuration.yaml

Even though configure-ovs uses in-memory profiles to ensure we are starting with a clean slate on each boot, the OVS database may still have leftover artifacts in it. This causes issues if you try to switch to using NMState to manage br-ex because the entries conflict with what NMState does. This patch simply adds a call to delete br-ex from the ovsdb if it exists when we apply an NMState configuration.

openshift-ci-robot · 2025-07-01T16:27:20Z

@cybertron: This pull request references OPNET-681 which is a valid jira issue.

This pull request references Jira Issue OCPBUGS-57484, which is invalid:

expected the bug to target the "4.20.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Even though configure-ovs uses in-memory profiles to ensure we are starting with a clean slate on each boot, the OVS database may still have leftover artifacts in it. This causes issues if you try to switch to using NMState to manage br-ex because the entries conflict with what NMState does.

This patch simply adds a call to delete br-ex from the ovsdb if it exists when we apply an NMState configuration.

- What I did

- How to verify it

- Description for the changelog

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 · 2025-07-01T16:32:28Z

@cybertron: This pull request references OPNET-681 which is a valid jira issue.

This pull request references Jira Issue OCPBUGS-57484, which is invalid:

expected the bug to target the "4.20.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

This PR adds logic to handle two migration paths to NMState: one from an existing OVNK cluster using configure-ovs, and one from OpenShift SDN directly to NMState without ever using configure-ovs.

In the former case, we need to clean up the left over remnants of configure-ovs's br-ex configuration. In the latter we need to clean up br0, which would otherwise have been done by configure-ovs.

- What I did

- How to verify it

- Description for the changelog

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.

cybertron · 2025-07-01T16:33:49Z

/jira refresh

openshift-ci-robot · 2025-07-01T16:33:57Z

@cybertron: This pull request references OPNET-681 which is a valid jira issue.

This pull request references Jira Issue OCPBUGS-57484, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.0) matches configured target version for branch (4.20.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @rbbratta

In response to this:

/jira refresh

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.

pliurh · 2025-07-02T01:57:39Z

templates/common/_base/files/nmstate-configuration.yaml

+    ovs-vsctl --timeout=30 --if-exists del-br br-ex
+
+    # Handle the case where we're migrating from OpenShift SDN
+    ovs-vsctl --timeout=30 --if-exists del-br br0


Can this script be invoked when a node is running with SDN? If yes, we cannot remove br0 in that case.

This should not be used with OpenShift SDN. It's specific to configuring br-ex for OVNKubernetes.

rbbratta · 2025-07-09T16:18:41Z

doesn't seem to work, or it didn't delete br0

rbbratta · 2025-07-09T16:31:41Z

Nevermind, bad NMstate failed to create br-ex so we fell back to SDN.

rbbratta · 2025-07-10T19:43:45Z

tested with MachineConfig. OVN-K migration successful.

Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + systemctl -q is-enabled mtu-migration
Jul 10 09:23:25 master-0 systemd[1]: Starting Applies per-node NMState network configuration...
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + echo 'Cleaning up left over mtu migration configuration'
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: Cleaning up left over mtu migration configuration
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + rm -rf /etc/cno/mtu-migration
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + '[' -e /etc/nmstate/openshift/applied ']'
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + src_path=/etc/nmstate/openshift
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + dst_path=/etc/nmstate
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2925]: ++ hostname -s
Jul 10 09:23:25 master-0 systemd[1]: nmstate-configuration.service: Deactivated successfully.
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + hostname=master-0
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + host_file=master-0.yml
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + cluster_file=cluster.yml
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + config_file=
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + '[' -s /etc/nmstate/openshift/master-0.yml ']'
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + '[' -s /etc/nmstate/openshift/cluster.yml ']'
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + echo 'No configuration found at /etc/nmstate/openshift/master-0.yml or /etc/nmstate/openshift/cluster.yml'
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: No configuration found at /etc/nmstate/openshift/master-0.yml or /etc/nmstate/openshift/cluster.yml
Jul 10 09:23:25 master-0 nmstate-configuration.sh[2922]: + exit 0
Jul 10 09:23:25 master-0 systemd[1]: Finished Applies per-node NMState network configuration.
-- Boot 745815ea8183486a800066fba3ac5a45 --
Jul 10 13:38:35 master-0 systemd[1]: Starting Applies per-node NMState network configuration...
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + systemctl -q is-enabled mtu-migration
Jul 10 13:38:35 master-0 systemctl[2881]: Failed to get unit file state for mtu-migration.service: No such file or directory
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + echo 'Cleaning up left over mtu migration configuration'
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: Cleaning up left over mtu migration configuration
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + rm -rf /etc/cno/mtu-migration
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + '[' -e /etc/nmstate/openshift/applied ']'
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + src_path=/etc/nmstate/openshift
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + dst_path=/etc/nmstate
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2883]: ++ hostname -s
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + hostname=master-0
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + host_file=master-0.yml
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + cluster_file=cluster.yml
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + config_file=
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + '[' -s /etc/nmstate/openshift/master-0.yml ']'
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + config_file=master-0.yml
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + '[' -e /etc/nmstate/master-0.yml ']'
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + ovs-vsctl --timeout=30 --if-exists del-br br-ex
Jul 10 13:38:35 master-0 ovs-vsctl[2884]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=30 --if-exists del-br br-ex
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + ovs-vsctl --timeout=30 --if-exists del-br br0
Jul 10 13:38:35 master-0 ovs-vsctl[2885]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=30 --if-exists del-br br0
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + cp /etc/nmstate/openshift/master-0.yml /etc/nmstate
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + touch /etc/nmstate/openshift/applied
Jul 10 13:38:35 master-0 systemd[1]: nmstate-configuration.service: Deactivated successfully.
Jul 10 13:38:35 master-0 systemd[1]: Finished Applies per-node NMState network configuration.
-- Boot bb3fff735d384e9bb420bb073d5e8f07 --
Jul 10 14:08:03 master-0 nmstate-configuration.sh[2902]: + systemctl -q is-enabled mtu-migration
Jul 10 14:08:03 master-0 systemd[1]: Starting Applies per-node NMState network configuration...
Jul 10 14:08:03 master-0 nmstate-configuration.sh[2902]: + '[' -e /etc/nmstate/openshift/applied ']'
Jul 10 14:08:03 master-0 nmstate-configuration.sh[2902]: + echo 'Configuration already applied, exiting'
Jul 10 14:08:03 master-0 nmstate-configuration.sh[2902]: Configuration already applied, exiting
Jul 10 14:08:03 master-0 nmstate-configuration.sh[2902]: + exit 0
Jul 10 14:08:03 master-0 systemd[1]: nmstate-configuration.service: Deactivated successfully.
Jul 10 14:08:03 master-0 systemd[1]: Finished Applies per-node NMState network configuration.
-- Boot ec2d04badfa84e14aa161c780a88a157 --
Jul 10 14:29:51 master-0 nmstate-configuration.sh[3066]: + systemctl -q is-enabled mtu-migration
Jul 10 14:29:51 master-0 systemd[1]: Starting Applies per-node NMState network configuration...
Jul 10 14:29:51 master-0 nmstate-configuration.sh[3066]: + echo 'Cleaning up left over mtu migration configuration'
Jul 10 14:29:51 master-0 nmstate-configuration.sh[3066]: Cleaning up left over mtu migration configuration
Jul 10 14:29:51 master-0 nmstate-configuration.sh[3066]: + rm -rf /etc/cno/mtu-migration
Jul 10 14:29:51 master-0 nmstate-configuration.sh[3066]: + '[' -e /etc/nmstate/openshift/applied ']'
Jul 10 14:29:51 master-0 nmstate-configuration.sh[3066]: + echo 'Configuration already applied, exiting'
Jul 10 14:29:51 master-0 nmstate-configuration.sh[3066]: Configuration already applied, exiting
Jul 10 14:29:51 master-0 nmstate-configuration.sh[3066]: + exit 0
Jul 10 14:29:51 master-0 systemd[1]: nmstate-configuration.service: Deactivated successfully.
Jul 10 14:29:51 master-0 systemd[1]: Finished Applies per-node NMState network configuration.

rbbratta · 2025-07-10T19:47:17Z

Jul 10 13:37:35 master-0 kernel: device br0 entered promiscuous mode
Jul 10 13:37:35 master-0 NetworkManager[1700]: <info>  [1752154655.2535] manager: (br0): new Open vSwitch Interface device (/org/freedesktop/NetworkManager/Devices/2)
Jul 10 13:37:35 master-0 NetworkManager[1700]: <info>  [1752154655.2912] manager: (br0): new Open vSwitch Port device (/org/freedesktop/NetworkManager/Devices/16)
Jul 10 13:37:35 master-0 NetworkManager[1700]: <info>  [1752154655.2944] manager: (br0): new Open vSwitch Bridge device (/org/freedesktop/NetworkManager/Devices/25)
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + systemctl -q is-enabled mtu-migration
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + echo 'Cleaning up left over mtu migration configuration'
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: Cleaning up left over mtu migration configuration
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + rm -rf /etc/cno/mtu-migration
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + '[' -e /etc/nmstate/openshift/applied ']'
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + src_path=/etc/nmstate/openshift
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + dst_path=/etc/nmstate
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2883]: ++ hostname -s
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + hostname=master-0
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + host_file=master-0.yml
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + cluster_file=cluster.yml
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + config_file=
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + '[' -s /etc/nmstate/openshift/master-0.yml ']'
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + config_file=master-0.yml
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + '[' -e /etc/nmstate/master-0.yml ']'
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + ovs-vsctl --timeout=30 --if-exists del-br br-ex
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + ovs-vsctl --timeout=30 --if-exists del-br br0
Jul 10 13:38:35 master-0 ovs-vsctl[2885]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=30 --if-exists del-br br0
Jul 10 13:38:35 master-0 ovs-vswitchd[1592]: ovs|00174|bridge|INFO|bridge br0: deleted interface br0 on port 65534
Jul 10 13:38:35 master-0 ovs-vswitchd[1592]: ovs|00175|bridge|INFO|bridge br0: deleted interface vxlan0 on port 1
Jul 10 13:38:35 master-0 ovs-vswitchd[1592]: ovs|00176|bridge|INFO|bridge br0: deleted interface tun0 on port 2
Jul 10 13:38:35 master-0 kernel: device br0 left promiscuous mode
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + cp /etc/nmstate/openshift/master-0.yml /etc/nmstate
Jul 10 13:38:35 master-0 nmstate-configuration.sh[2880]: + touch /etc/nmstate/openshift/applied
Jul 10 13:38:35 master-0 systemd[1]: nmstate-configuration.service: Deactivated successfully.

rbbratta · 2025-07-10T19:47:36Z

/label qe-approved

cybertron · 2025-07-23T13:54:26Z

/retest-required

I see a string of passes from yesterday. Maybe this is fixed?

mkowalski · 2025-07-24T07:40:39Z

/lgtm

cybertron · 2025-07-24T14:02:58Z

/assign @djoshy

djoshy · 2025-07-24T14:21:38Z

/approve

/retest-required

I see a string of passes from yesterday. Maybe this is fixed?

Hopefully - we think #5184 was the issue

openshift-ci · 2025-07-24T14:24:27Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cybertron, djoshy, mkowalski

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

~~OWNERS~~ [djoshy]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci-robot · 2025-07-24T15:41:30Z

/retest-required

Remaining retests: 0 against base HEAD 30e1d23 and 2 for PR HEAD 12878e4 in total

openshift-ci-robot · 2025-07-24T16:45:39Z

/retest-required

Remaining retests: 0 against base HEAD ab14c8e and 1 for PR HEAD 12878e4 in total

openshift-ci-robot · 2025-07-24T21:41:10Z

/retest-required

Remaining retests: 0 against base HEAD ab14c8e and 2 for PR HEAD 12878e4 in total

openshift-ci-robot · 2025-07-25T04:58:56Z

/retest-required

Remaining retests: 0 against base HEAD 8a0a7fe and 2 for PR HEAD 12878e4 in total

openshift-ci-robot · 2025-07-28T19:03:58Z

/retest-required

Remaining retests: 0 against base HEAD f98561d and 2 for PR HEAD 12878e4 in total

openshift-ci-robot · 2025-07-29T00:06:48Z

/retest-required

Remaining retests: 0 against base HEAD f98561d and 2 for PR HEAD 12878e4 in total

openshift-ci · 2025-07-29T04:14:05Z

@cybertron: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-hypershift-techpreview	`7536665`	link	false	`/test e2e-hypershift-techpreview`
ci/prow/bootstrap-unit	`12878e4`	link	false	`/test bootstrap-unit`
ci/prow/okd-scos-e2e-aws-ovn	`12878e4`	link	false	`/test okd-scos-e2e-aws-ovn`
ci/prow/e2e-gcp-op-ocl	`12878e4`	link	false	`/test e2e-gcp-op-ocl`
ci/prow/e2e-aws-ovn-windows	`12878e4`	link	false	`/test e2e-aws-ovn-windows`
ci/prow/e2e-azure-ovn-upgrade-out-of-change	`12878e4`	link	false	`/test e2e-azure-ovn-upgrade-out-of-change`
ci/prow/e2e-aws-ovn-upgrade-out-of-change	`12878e4`	link	false	`/test e2e-aws-ovn-upgrade-out-of-change`

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 · 2025-07-29T05:06:38Z

/retest-required

Remaining retests: 0 against base HEAD b86adc7 and 1 for PR HEAD 12878e4 in total

openshift-ci-robot · 2025-07-29T14:05:56Z

@cybertron: Jira Issue OCPBUGS-57484: All pull requests linked via external trackers have merged:

openshift/machine-config-operator#5064

Jira Issue OCPBUGS-57484 has been moved to the MODIFIED state.

In response to this:

This PR adds logic to handle two migration paths to NMState: one from an existing OVNK cluster using configure-ovs, and one from OpenShift SDN directly to NMState without ever using configure-ovs.

In the former case, we need to clean up the left over remnants of configure-ovs's br-ex configuration. In the latter we need to clean up br0, which would otherwise have been done by configure-ovs.

- What I did

- How to verify it

- Description for the changelog

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.

mkowalski · 2025-07-29T14:44:53Z

/jira backport release-4.19,release-4.18,release-4.17,release-4.16

openshift-ci-robot · 2025-07-29T14:45:30Z

@mkowalski: The following backport issues have been created:

OCPBUGS-59928 for branch release-4.19
OCPBUGS-59929 for branch release-4.18
OCPBUGS-59930 for branch release-4.17
OCPBUGS-59931 for branch release-4.16

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17
/cherrypick release-4.16

In response to this:

/jira backport release-4.19,release-4.18,release-4.17,release-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 openshift-eng/jira-lifecycle-plugin repository.

openshift-cherrypick-robot · 2025-07-29T14:46:14Z

@openshift-ci-robot: new pull request created: #5205

In response to this:

@mkowalski: The following backport issues have been created:

OCPBUGS-59928 for branch release-4.19

OCPBUGS-59929 for branch release-4.18

OCPBUGS-59930 for branch release-4.17

OCPBUGS-59931 for branch release-4.16

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17
/cherrypick release-4.16

In response to this:

/jira backport release-4.19,release-4.18,release-4.17,release-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 openshift-eng/jira-lifecycle-plugin repository.

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 · 2025-07-29T14:46:56Z

@openshift-ci-robot: new pull request created: #5206

In response to this:

@mkowalski: The following backport issues have been created:

OCPBUGS-59928 for branch release-4.19

OCPBUGS-59929 for branch release-4.18

OCPBUGS-59930 for branch release-4.17

OCPBUGS-59931 for branch release-4.16

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17
/cherrypick release-4.16

In response to this:

/jira backport release-4.19,release-4.18,release-4.17,release-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 openshift-eng/jira-lifecycle-plugin repository.

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 · 2025-07-29T14:47:38Z

@openshift-ci-robot: new pull request created: #5207

In response to this:

@mkowalski: The following backport issues have been created:

OCPBUGS-59928 for branch release-4.19

OCPBUGS-59929 for branch release-4.18

OCPBUGS-59930 for branch release-4.17

OCPBUGS-59931 for branch release-4.16

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17
/cherrypick release-4.16

In response to this:

/jira backport release-4.19,release-4.18,release-4.17,release-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 openshift-eng/jira-lifecycle-plugin repository.

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 · 2025-07-29T14:48:19Z

@openshift-ci-robot: new pull request created: #5208

In response to this:

@mkowalski: The following backport issues have been created:

OCPBUGS-59928 for branch release-4.19

OCPBUGS-59929 for branch release-4.18

OCPBUGS-59930 for branch release-4.17

OCPBUGS-59931 for branch release-4.16

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17
/cherrypick release-4.16

In response to this:

/jira backport release-4.19,release-4.18,release-4.17,release-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 openshift-eng/jira-lifecycle-plugin repository.

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-bot · 2025-07-29T22:37:07Z

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-config-operator
This PR has been included in build ose-machine-config-operator-container-v4.20.0-202507291516.p0.g46bdad2.assembly.stream.el9.
All builds following this will include this PR.

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 19, 2025

openshift-ci bot requested review from dkhater-redhat and yuqi-zhang May 19, 2025 21:00

openshift-ci bot requested review from emy and mkowalski June 17, 2025 17:24

rbbratta reviewed Jun 18, 2025

View reviewed changes

templates/common/_base/files/nmstate-configuration.yaml Outdated Show resolved Hide resolved

cybertron added 2 commits July 1, 2025 11:19

OCPBUGS-57484: Handle migration from OpenShift SDN

12878e4

cybertron force-pushed the nmstate-migration branch from 7536665 to 12878e4 Compare July 1, 2025 16:21

cybertron changed the title ~~OPNET-681: Support migration from configure-ovs to NMState~~ OPNET-681,OCPBUGS-57484: Support migration to NMState Jul 1, 2025

openshift-ci-robot added the jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. label Jul 1, 2025

openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jul 1, 2025

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 1, 2025

openshift-ci bot requested a review from rbbratta July 1, 2025 16:33

pliurh reviewed Jul 2, 2025

View reviewed changes

openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jul 10, 2025

openshift-ci bot assigned mkowalski Jul 24, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 24, 2025

openshift-ci bot assigned djoshy Jul 24, 2025

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 24, 2025

openshift-merge-bot bot merged commit 46bdad2 into openshift:main Jul 29, 2025
14 of 20 checks passed

openshift-cherrypick-robot mentioned this pull request Jul 29, 2025

[release-4.16] OPNET-681,OCPBUGS-59931: Support migration to NMState #5205

Open

openshift-cherrypick-robot mentioned this pull request Jul 29, 2025

[release-4.17] OPNET-681,OCPBUGS-59930: Support migration to NMState #5206

Merged

openshift-cherrypick-robot mentioned this pull request Jul 29, 2025

[release-4.18] OPNET-681,OCPBUGS-59929: Support migration to NMState #5207

Merged

openshift-cherrypick-robot mentioned this pull request Jul 29, 2025

[release-4.19] OPNET-681,OCPBUGS-59928: Support migration to NMState #5208

Merged

OPNET-681,OCPBUGS-57484: Support migration to NMState #5064

OPNET-681,OCPBUGS-57484: Support migration to NMState #5064

Uh oh!

Conversation

cybertron commented May 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented May 19, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cybertron commented May 22, 2025

Uh oh!

yuqi-zhang commented May 22, 2025

Uh oh!

cybertron commented Jun 17, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented Jul 1, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Jul 1, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cybertron commented Jul 1, 2025

Uh oh!

openshift-ci-robot commented Jul 1, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pliurh Jul 2, 2025

Choose a reason for hiding this comment

Uh oh!

cybertron Jul 2, 2025

Choose a reason for hiding this comment

Uh oh!

rbbratta commented Jul 9, 2025

Uh oh!

rbbratta commented Jul 9, 2025

Uh oh!

rbbratta commented Jul 10, 2025

Uh oh!

rbbratta commented Jul 10, 2025

Uh oh!

rbbratta commented Jul 10, 2025

Uh oh!

cybertron commented Jul 23, 2025

Uh oh!

mkowalski commented Jul 24, 2025

Uh oh!

cybertron commented Jul 24, 2025

Uh oh!

djoshy commented Jul 24, 2025

Uh oh!

openshift-ci bot commented Jul 24, 2025

Uh oh!

openshift-ci-robot commented Jul 24, 2025

Uh oh!

openshift-ci-robot commented Jul 24, 2025

Uh oh!

openshift-ci-robot commented Jul 24, 2025

Uh oh!

openshift-ci-robot commented Jul 25, 2025

Uh oh!

openshift-ci-robot commented Jul 28, 2025

Uh oh!

openshift-ci-robot commented Jul 29, 2025

Uh oh!

openshift-ci bot commented Jul 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Jul 29, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented Jul 29, 2025

Uh oh!

mkowalski commented Jul 29, 2025

Uh oh!

openshift-ci-robot commented Jul 29, 2025

Uh oh!

openshift-cherrypick-robot commented Jul 29, 2025

Uh oh!

cybertron commented May 19, 2025 •

edited

Loading

openshift-ci-robot commented May 19, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Jul 1, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Jul 1, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Jul 1, 2025 •

edited by openshift-ci bot

Loading

openshift-ci bot commented Jul 29, 2025 •

edited

Loading