search

openshift / openshift-ansible

Install and config an OpenShift 3.x cluster
https://try.openshift.com
Apache License 2.0
2.19k stars 2.31k forks source link

OCPBUGS-39178: Update the network backend of podman to Netavark if installing Podman 5.0 and higher #12514

Closed gpei closed 2 months ago

gpei commented 2 months ago

CNI network backend is not supported anymore since Podman version 5.0[1], now we've got podman-5.2.0-3.rhaos4.17.el8.x86_64 installed from the OCP-4.17 RHEL-8 repo, but the network backend is still configured as "cni" by default in /usr/share/containers/containers.conf, so update the network_backend option to "netavark" when installing podman-5.0.x and higher, which also requiring the "netavark" related packages.

[1]https://docs.podman.io/en/latest/markdown/podman-network.1.html

openshift-ci-robot commented 2 months ago

@gpei: This pull request references Jira Issue OCPBUGS-39178, which is invalid:

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](https://github.com/openshift/openshift-ansible/pull/12514): >CNI network backend is not supported anymore since Podman version 5.0[1], now we've got podman-5.2.0-3.rhaos4.17.el8.x86_64 installed from the OCP-4.17 RHEL-8 repo, but the network backend is still configured as "cni" by default in /usr/share/containers/containers.conf, so update the `network_backend` option to "netavark" when installing podman-5.0.x and higher, which also requiring the "netavark" related packages. > > > >[1]https://docs.podman.io/en/latest/markdown/podman-network.1.html Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-ansible). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
gpei commented 2 months ago

/retest

gpei commented 2 months ago

/test e2e-aws-workers-rhel8

gpei commented 2 months ago

/jira refresh

openshift-ci-robot commented 2 months ago

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

Requesting review from QA contact: /cc @gpei

In response to [this](https://github.com/openshift/openshift-ansible/pull/12514#issuecomment-2320746481): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-ansible). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-ci[bot] commented 2 months ago

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: gpei.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to [this](https://github.com/openshift/openshift-ansible/pull/12514#issuecomment-2320746705): >@gpei: This pull request references [Jira Issue OCPBUGS-39178](https://issues.redhat.com//browse/OCPBUGS-39178), 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.18.0) matches configured target version for branch (4.18.0) >* bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact: /cc @gpei

In response to [this](https://github.com/openshift/openshift-ansible/pull/12514#issuecomment-2320746481): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-ansible). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) 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.

gpei commented 2 months ago

/retest

openshift-ci[bot] commented 2 months ago

@gpei: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
openshift-ci[bot] commented 2 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: barbacbd, gpei

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](https://github.com/openshift/openshift-ansible/blob/master/OWNERS)~~ [barbacbd] 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 commented 2 months ago

@gpei: Jira Issue OCPBUGS-39178: All pull requests linked via external trackers have merged:

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

In response to [this](https://github.com/openshift/openshift-ansible/pull/12514): >CNI network backend is not supported anymore since Podman version 5.0[1], now we've got podman-5.2.0-3.rhaos4.17.el8.x86_64 installed from the OCP-4.17 RHEL-8 repo, but the network backend is still configured as "cni" by default in /usr/share/containers/containers.conf, so update the `network_backend` option to "netavark" when installing podman-5.0.x and higher, which also requiring the "netavark" related packages. > > > >[1]https://docs.podman.io/en/latest/markdown/podman-network.1.html Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-ansible). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
gpei commented 2 months ago

/cherry-pick release-4.17

openshift-cherrypick-robot commented 2 months ago

@gpei: new pull request created: #12515

In response to [this](https://github.com/openshift/openshift-ansible/pull/12514#issuecomment-2327710349): >/cherry-pick release-4.17 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.