Skip to content

[release-5.0] USHIFT-7501: Stop openvswitch after OVN cleanup in microshift-cleanup-data - #7365

Open
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-5.0from
openshift-cherrypick-robot:cherry-pick-7347-to-release-5.0
Open

[release-5.0] USHIFT-7501: Stop openvswitch after OVN cleanup in microshift-cleanup-data#7365
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-5.0from
openshift-cherrypick-robot:cherry-pick-7347-to-release-5.0

Conversation

@openshift-cherrypick-robot

@openshift-cherrypick-robot openshift-cherrypick-robot commented Sep 10, 2026

Copy link
Copy Markdown

This is an automated cherry-pick of #7347

/assign agullon

@agullon @openshift-cherrypick-robot
USHIFT-7501: Stop openvswitch after OVN cleanup in microshift-cleanup…
056b33c 
…-data

After `microshift-cleanup-data --all` (or `--ovn`) stops ovsdb-server and
kills the OVN processes, ovs-vswitchd is left running without its database,
so stale OVS datapath/flow state persists. On the next MicroShift start
ovnkube-node fatals during init while clearing stale OVS flow targets:

  failed to init default node network controller:
  error clearing stale ovs flow targets: "exit status 1"

ovnkube-node then crash-loops, never writes the node chassis / gateway
config, and every pod is stuck FailedCreatePodSandBox / NetworkPluginNotReady
until the healthcheck times out. This was observed intermittently under heavy
full-optional load (e.g. the el98-lrel@optional release scenario).

Stop openvswitch.service after the OVN process cleanup so the stale state is
cleared. The next MicroShift start brings openvswitch back up via
microshift.service's Wants and microshift-ovs-init.service's Requires, giving
OVN a clean slate to reinitialize. Unlike the best-effort kills above, a real
stop failure here has a correctness impact, so it is surfaced rather than
discarded.

The underlying fragility (ovnkube-node treating the ovs-vsctl failure as
fatal) is upstream ovn-kubernetes; this change removes the precondition on
the MicroShift side.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

pre-commit.check-secrets: ENABLED
@openshift-merge-bot

openshift-merge-bot Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Sep 10, 2026
Merged
@openshift-ci-robot

openshift-ci-robot commented Sep 10, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: USHIFT-7501

Details

In response to this:

This is an automated cherry-pick of #7347

/assign agullon

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.

@coderabbitai

coderabbitai Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 2f4fd370-b992-4935-aaa3-4b898e4d3a31

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@openshift-ci
openshift-ci Bot requested review from jerpeter1 and jogeo September 10, 2026 12:08
@openshift-ci

openshift-ci Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign agullon for approval. For more information see the Code Review Process.

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

Details Needs approval from an approver in each of these files:

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

@agullon

agullon commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

/pipeline required

@openshift-merge-bot

openshift-merge-bot Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-tests
/test e2e-aws-tests-arm
/test e2e-aws-tests-bootc-arm-el10
/test e2e-aws-tests-bootc-arm-el9
/test e2e-aws-tests-bootc-el10
/test e2e-aws-tests-bootc-el9

@agullon

agullon commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 10, 2026
@agullon

agullon commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

/test e2e-aws-tests-release
/test e2e-aws-tests-release-arm
/test e2e-aws-tests-bootc-release-el9
/test e2e-aws-tests-bootc-release-el10
/test e2e-aws-tests-bootc-release-arm-el9
/test e2e-aws-tests-bootc-release-arm-el10

@openshift-ci

openshift-ci Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: 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-aws-tests-bootc-release-el10 056b33c link true /test e2e-aws-tests-bootc-release-el10
ci/prow/e2e-aws-tests-bootc-el10 056b33c link true /test e2e-aws-tests-bootc-el10
ci/prow/e2e-aws-tests-release-arm 056b33c link true /test e2e-aws-tests-release-arm
ci/prow/e2e-aws-tests-bootc-release-arm-el9 056b33c link true /test e2e-aws-tests-bootc-release-arm-el9
ci/prow/e2e-aws-tests-bootc-release-arm-el10 056b33c link true /test e2e-aws-tests-bootc-release-arm-el10
ci/prow/e2e-aws-tests 056b33c link true /test e2e-aws-tests
ci/prow/e2e-aws-tests-bootc-release-el9 056b33c link true /test e2e-aws-tests-bootc-release-el9
ci/prow/e2e-aws-tests-release 056b33c link true /test e2e-aws-tests-release

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.

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

Reviewers

@jerpeter1 jerpeter1 Awaiting requested review from jerpeter1
@jogeo jogeo Awaiting requested review from jogeo

Assignees

@agullon agullon

Labels

backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@openshift-cherrypick-robot @openshift-ci-robot @agullon