Bug 1579445
Summary: | cri-o package should not add /cni/net.d/ configurations files on install | ||||||
---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ryan Howe <rhowe> | ||||
Component: | Node | Assignee: | Jindrich Novy <jnovy> | ||||
Status: | CLOSED ERRATA | QA Contact: | weiwei jiang <wjiang> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.11.0 | CC: | amurdaca, andcosta, aos-bugs, dornelas, dwalsh, erich, farandac, hgomes, hongli, jnovy, jokerman, lsm5, mmccomas, mpatel, pamadio, ph.hutter, umohnani | ||||
Target Milestone: | --- | Keywords: | Reopened | ||||
Target Release: | 3.11.z | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | cri-o-1.11.16-0.4.dev.rhaos3.11.git3f89eba.el7 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-12-16 11:57:10 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1186913 | ||||||
Attachments: |
|
Description
Ryan Howe
2018-05-17 16:41:33 UTC
Also this when cri-o is enabled on an OpenShift node and then cri-o is updated it will add these back on the host. # rm /etc/cni/net.d/200-loopback.conf # rm /etc/cni/net.d/100-crio-bridge.conf # yum update cri-o # ls /etc/cni/net.d/ 100-crio-bridge.conf 200-loopback.conf 80-openshift-network.conf Causing the OpenShift node to fail to start pods with erro "Error while adding to cni network: failed to find plugin "bridge" in path [/opt/bridge/bin /opt/cni/bin]" Manual deletion is needed then. mmm I'm fine removing those configurations and provide them as another cri-o-cni-configs RPM. We can suggest people to install this new package when running CRI-O w/o openshift or with kube. Lokesh, can we ship such an RPM containing just CNI config files? Mrunal, Dan, wdyt? I believe this is not a 3.10 blocker though. The installer takes care of the network just fine, this is an edge case when CRI-O is installed prior to installing openshift. I'm removing this from 3.10 but feel free to move it back if you think so. Hi, We have another customer asking to see if it is possible to add cri-o to the atomic-openshift-excluder or create one like we have for docker. Every time we update system and cri-o gets updated it will add the files already mentioned in this bugzila. Or you can rename the files because now following that order the atomic-openshift-node service will fail since 80-openshift-network.conf gets in the last place. I'm uploading an example I did with OCP 3.11 repos. Thanks, Created attachment 1510852 [details]
Yum update cri-o example
(In reply to Antonio Murdaca from comment #2) > mmm I'm fine removing those configurations and provide them as another > cri-o-cni-configs RPM. We can suggest people to install this new package > when running CRI-O w/o openshift or with kube. > Lokesh, can we ship such an RPM containing just CNI config files? > Mrunal, Dan, wdyt? Frantisek, can you please make this change ^ Lokesh can you take this over. OCP 3.6-3.10 is no longer on full support [1]. Marking CLOSED DEFERRED. If you have a customer case with a support exception or have reproduced on 3.11+, please reopen and include those details. When reopening, please set the Target Release to the appropriate version where needed. [1]: https://access.redhat.com/support/policy/updates/openshift OCP 3.6-3.10 is no longer on full support [1]. Marking CLOSED DEFERRED. If you have a customer case with a support exception or have reproduced on 3.11+, please reopen and include those details. When reopening, please set the Target Release to the appropriate version where needed. [1]: https://access.redhat.com/support/policy/updates/openshift Hello, This is for OCP 3.11 which is the current version on the customer and I was able to reproduce this issue recently. Verified with cri-o-1.11.16-0.4.dev.rhaos3.11.git3f89eba.el7 # rpm -ql cri-o /etc/crictl.yaml /etc/crio /etc/crio/crio.conf /etc/crio/seccomp.json /etc/sysconfig/crio-network /etc/sysconfig/crio-storage /usr/bin/crio /usr/lib/systemd/system/cri-o.service /usr/lib/systemd/system/crio-shutdown.service /usr/lib/systemd/system/crio.service /usr/libexec/crio /usr/libexec/crio/conmon /usr/libexec/crio/pause /usr/share/doc/cri-o-1.11.16 /usr/share/doc/cri-o-1.11.16/README.md /usr/share/licenses/cri-o-1.11.16 /usr/share/licenses/cri-o-1.11.16/LICENSE /usr/share/man/man5/crio.conf.5.gz /usr/share/man/man8/crio.8.gz /usr/share/oci-umount /usr/share/oci-umount/oci-umount.d /usr/share/oci-umount/oci-umount.d/crio-umount.conf /var/lib/containers # rpm -qa|grep -i cri-o cri-o-1.11.16-0.4.dev.rhaos3.11.git3f89eba.el7.x86_64 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:4050 |