Description of problem: After upgrading RHVH to 4.4.6 seeing continues message /usr/lib/systemd/system/virtproxyd.socket:4: Missing '='. Version-Release number of selected component (if applicable): RHVH 4.4.6 Additional info: Workaround to stop messages : $ vi /usr/lib/systemd/system/virtproxyd.socket # in front of libvirtd.socket libvirtd-ro.socket libvirtd-admin.socket libvirtd-tcp.socket libvirtd-tls.socket restart virtproxyd.socket
QE reproduced this bug. Test Versions: RHVM: 4.4.7.6-0.11.el8ev RHVH: upgrade rhvh from rhvh-4.4.5.4-0.20210330.0+1 to rhvh-4.4.6.2-0.20210615.0+1 Test Steps: 1. Install redhat-virtualization-host-4.4.5-20210330.0.el8_3 2. Add host to RHVM 3. Login to host, setup local repos and point to "redhat-virtualization-host-4.4.6-20210615.0.el8_4" 4. Upgrade the host via RHVM 5. Check the service "virtproxyd.socket" # systemctl status virtproxyd.socket Test Result: After upgrade: ~~~~~~ # systemctl status virtproxyd.socket ● virtproxyd.socket - Libvirt proxy local socket Loaded: error (Reason: Unit virtproxyd.socket failed to loaded properly: Invalid argument.) Active: inactive (dead) Jul 20 03:01:01 dell-per730-35.lab.eng.pek2.redhat.com systemd[1]: /usr/lib/systemd/system/virtproxyd.socket:4: Missing '=> ~~~~~~ logs from /var/log/messages ~~~~~~ Jul 20 03:01:01 dell-per730-35 systemd[1]: /usr/lib/systemd/system/virtproxyd.socket:4: Missing '='. Jul 20 03:01:01 dell-per730-35 systemd[1]: /usr/lib/systemd/system/virtproxyd-admin.socket:6: Missing '='. Jul 20 03:01:01 dell-per730-35 systemd[1]: /usr/lib/systemd/system/virtproxyd-ro.socket:6: Missing '='. ~~~~~~ I noticed that in the clean installation of rhvh-4.4.5.4-0.20210330.0+1, the status of “virtproxyd.socket” is “inactive (dead)”. For this issue, what should be the correct result? Should “virtproxyd.socket” be active by default? Or, there should be no error messages(/usr/lib/systemd/system/virtproxyd.socket:4: Missing '='.) when running/checking “virtproxyd.socket” ？
Moving to RHEL-AV
# rpm -qf /usr/lib/systemd/system/virtproxyd.socket libvirt-daemon-7.0.0-14.3.module+el8.4.0+11878+84e54169.x86_64 outside RHV-H also have the same issue.
There is a bug here: Bug 1917302 Hi, Pavel. Do we need a backport here?
Would be nice to have in 8.4 upcoming batch
*** This bug has been marked as a duplicate of bug 1917302 ***