-
Notifications
You must be signed in to change notification settings - Fork 596
Sos openshift ovn enable by crio containers #4123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sos openshift ovn enable by crio containers #4123
Conversation
|
Congratulations! One of the builds has completed. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
2 similar comments
|
Congratulations! One of the builds has completed. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
|
Congratulations! One of the builds has completed. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
This will allow containers = (..) to be checked against given runtime, if it is not default one. Related: sosreport#4123 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
OpenShift OVN has both podman and crio runtimes and sos detects podman as the default one. While the containers triggering openshift_ovn enabledness are under 'crio' runtime. Closes: sosreport#4123 Relevant: RHEL-110512 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
a7f34dc to
10a2c59
Compare
This will allow containers = (..) to be checked against given runtime, if it is not default one. Related: #4123 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
This will allow containers = (..) to be checked against given runtime, if it is not default one. Related: sosreport#4123 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
OpenShift OVN has both podman and crio runtimes and sos detects podman as the default one. While the containers triggering openshift_ovn enabledness are under 'crio' runtime. Closes: sosreport#4123 Relevant: RHEL-110512 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
This will allow containers = (..) to be checked against given runtime, if it is not default one. Related: sosreport#4123 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
OpenShift OVN has both podman and crio runtimes and sos detects podman as the default one. While the containers triggering openshift_ovn enabledness are under 'crio' runtime. Closes: sosreport#4123 Relevant: RHEL-110512 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
OpenShift OVN has both
podmanandcrioruntimes and sos detectspodmanas the default one. While the containers triggeringopenshift_ovnenabledness are undercrioruntime.To proper plugin enabledness detection, we must make the runtime customisable.
Closes: #4123
Relevant: RHEL-110512
Please place an 'X' inside each '[]' to confirm you adhere to our Contributor Guidelines