There is also a side effect, that traceback appears in /var/log/up2date: Traceback (most recent call last): File "/usr/sbin/rhnreg_ks", line 227, in ? cli.run() File "/usr/share/rhn/up2date_client/rhncli.py", line 66, in run sys.exit(self.main() or 0) File "/usr/sbin/rhnreg_ks", line 178, in main rhnreg.sendVirtInfo(systemId) File "/usr/share/rhn/up2date_client/rhnreg.py", line 674, in sendVirtInfo support.refresh() File "/usr/share/rhn/virtualization/support.py", line 51, in refresh if _is_host_domain(): File "/usr/share/rhn/virtualization/support.py", line 161, in _is_host_domain conn = libvirt.open(None) File "/usr/lib64/python2.4/site-packages/libvirt.py", line 169, in open if ret is None:raise libvirtError('virConnectOpen() failed')
Looks like this is not an issue with rhn-virtualization-host-5.4.14-8.el5sat.
Package rhn-virtualization-host-5.4.14-8.el5sat do *not* fix issue with rhn-profile-sync which still returns 0 even after it is unable to update virtualization profile.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Confirmed that latest rhn-virtualization-host package makes rhnreg_ks exit with exit status 0 and that rhn-profile-sync still exits with exit status 0 even though it should not (see discussion in bug 714903).
Committed as 208756. Note that this requires rhn-virtualization-host-5.4.34-3 which will be released with Sat 5.5.
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. http://rhn.redhat.com/errata/RHBA-2013-0104.html