Bug 2084171
Summary: | [c9s] failing to setup network | ||
---|---|---|---|
Product: | [oVirt] vdsm | Reporter: | Sandro Bonazzola <sbonazzo> |
Component: | SuperVDSM | Assignee: | eraviv |
Status: | CLOSED UPSTREAM | QA Contact: | eraviv |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.50.0.13 | CC: | amusil, bugs, eraviv, mburman, mperina |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-10-05 11:21:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2084118, 2121315, 2148207 | ||
Bug Blocks: |
Description
Sandro Bonazzola
2022-05-11 15:05:04 UTC
Looks like CentOS Stream 9 specific issue as deploy on Alma Linux 9.0 Beta works after executing: ausearch -c 'lldpad' --raw | audit2allow -M my-lldpad semodule -X 300 -i my-lldpad.pp ausearch -c 'modprobe' --raw | audit2allow -M my-modprobe semodule -X 300 -i my-modprobe.pp for handling selinux denials reported in the journal. Enabling oVirt 4.5 on Alma 9 beta: ``` cat >/etc/yum.repos.d/CentOS-Stream-Extras-common.repo <<'EOF' [c9s-extras-common] name=CentOS Stream $releasever - Extras packages metalink=https://mirrors.centos.org/metalink?repo=centos-extras-sig-extras-common-$stream&arch=$basearch&protocol=https,http gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Extras gpgcheck=1 repo_gpgcheck=0 metadata_expire=6h countme=1 enabled=1 EOF echo "9-stream" > /etc/yum/vars/stream dnf distro-sync --nobest ``` going to update the install guide with this once I get it a bit more tested. Hi, the selinux is probably new one, but the KeyError: 'ipv4' is due to backward incompatibility of nmstate-2.1. The reason why it works on Alma is probably that it has nmstate-2.0 which is still fine. The nmstate team is aware of that and hopefully the fix will land soon (PR is already posted). Based on above targeting to 4.5.1, let's see when relevant nmstate update will land in CS9 fails on a different issue (attached supervdsm log): Traceback (most recent call last): ..... File "/usr/lib/python3.9/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda> getattr(self._supervdsmProxy._svdsm, self._funcName)(*args, File "<string>", line 2, in setupNetworks File "/usr/lib64/python3.9/multiprocessing/managers.py", line 825, in _callmethod raise convert_to_error(kind, result) libnmstate.error.NmstateInternalError: DbusConnectionError: org.freedesktop.NetworkManager.Settings.Connection.InvalidProperty: connection.slave-type: A connection with a 'bridge-port' setting must have the slave-type set to 'bridge'. Instead it is 'bond' dbus: Some(MethodError("org.freedesktop.NetworkManager.Settings.Connection.InvalidProperty", Some("connection.slave-type: A connection with a 'bridge-port' setting must have the slave-type set to 'bridge'. Instead it is 'bond'"), Msg { type: Error, sender: ":1.6", reply-serial: 332, body: Signature: [ s (115), ] })) with: nmstate-libs-2.2.0-0.alpha.20220810.8e122d43.el9.x86_64 python3-libnmstate-2.2.0-0.alpha.20220810.8e122d43.el9.x86_64 Issue from comment #9 acked by nmstate team and dedicated bug #2121315 opened to track it. Adding 'depends on' it. Moving to https://github.com/oVirt/vdsm/issues/338 |