[release-4.17] OPNET-681,OCPBUGS-59930: Support migration to NMState #5206
Conversation
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-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OPNET-681 In response to this:
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
bot
changed the title
openshift-ci-robot
added
jira/severity-important
|
@openshift-cherrypick-robot: 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.20" instead. This pull request references Jira Issue OCPBUGS-59930, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
|
/lgtm |
|
/label qe-approved |
openshift-ci
bot
added
qe-approved
openshift-ci-robot
added
jira/valid-bug
|
@openshift-cherrypick-robot: 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 either version "4.17." or "openshift-4.17.", but it targets "openshift-4.20" instead. This pull request references Jira Issue OCPBUGS-59930, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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. |
|
/label backport-risk-assessed |
openshift-ci
bot
added
the
backport-risk-assessed
openshift-ci
bot
assigned
anuragthehatter,
eurijon,
imatza-rh,
lyman9966,
mhanss and
ptalgulk01
|
/override ci/prow/cluster-bootimages This is an old test that no longer works that was accidentally turned on due to some o/release config changes. The override may get lost in future reruns, so feel free to ping the forum to request another one. /retest-required |
|
@djoshy: Overrode contexts on behalf of djoshy: ci/prow/cluster-bootimages In response to this:
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. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: djoshy, mkowalski, openshift-cherrypick-robot 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:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
/override ci/prow/cluster-bootimages |
|
@djoshy: Overrode contexts on behalf of djoshy: ci/prow/cluster-bootimages In response to this:
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. |
5 similar comments
|
/override ci/prow/cluster-bootimages |
|
@djoshy: Overrode contexts on behalf of djoshy: ci/prow/cluster-bootimages In response to this:
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: The following tests failed, say
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. |
|
/verifed by @rbbratta |
|
/verified by @rbbratta |
openshift-ci-robot
added
the
verified
|
@rbbratta: This PR has been marked as verified by In response to this:
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-merge-bot
bot
merged commit d683459
into
openshift:release-4.17
|
@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-59930 Jira Issue OCPBUGS-59930 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 In response to this:
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. |
|
Fix included in accepted release 4.17.0-0.nightly-2025-09-03-012131 |
|
[ART PR BUILD NOTIFIER] Distgit: ose-machine-config-operator |
This is an automated cherry-pick of #5064
/assign openshift-ci-robot