OCPBUGS-104572: NetworkManager-ovs has moved up to RHCOS

[sdodson]

NetworkManager-ovs was being installed in the node-image layer (openshift/os) from OCP repos. Because the base image version-locks all its packages before the node layer runs, NetworkManager-ovs could end up at a different version than NetworkManager itself. Move it to the base image so both are sourced from the same RHEL repos and stay in sync.

Depends on coreos/rhel-coreos-config#296

[openshift-ci-robot]

@sdodson: This pull request references Jira Issue OCPBUGS-104572, 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 (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

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

Details

In response to this:

It's moving to rhcos layer

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]

@sdodson: This pull request references Jira Issue OCPBUGS-104572, which is valid.

3 validation(s) were run on this bug

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

Details

In response to this:

NetworkManager-ovs was being installed in the node-image layer (openshift/os) from OCP repos. Because the base image version-locks all its packages before the node layer runs, NetworkManager-ovs could end up at a different version than NetworkManager itself. Move it to the base image so both are sourced from the same RHEL repos and stay in sync.

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]

@sdodson: This pull request references Jira Issue OCPBUGS-104572, which is valid.

3 validation(s) were run on this bug

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

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

Details

In response to this:

NetworkManager-ovs was being installed in the node-image layer (openshift/os) from OCP repos. Because the base image version-locks all its packages before the node layer runs, NetworkManager-ovs could end up at a different version than NetworkManager itself. Move it to the base image so both are sourced from the same RHEL repos and stay in sync.

Depends on coreos/rhel-coreos-config#296

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.

[sdodson]

/hold
until the dependent PR merges

[Rolv-Apneseth]

/lgtm

[sdodson]

/retest-required

[aaradhak]

/retest

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aaradhak, Rolv-Apneseth, sdodson

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [Rolv-Apneseth,aaradhak]

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

[sdodson]

/test images

[openshift-ci]

@sdodson: The following test 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/images	497203d	link	true	/test images

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.