Description of problem: rhn-profile-sync utility (part of rhn-client-tools) does not properly update virtualization profile for KVM guests that have been powered off. Version-Release number of selected component (if applicable): rhn-client-tools-0.4.20-9.el5.noarch How reproducible: Always Steps to Reproduce: 1. Have a RHEL-5.4 (or later) x86_64 KVM host (hardware has to support full virtualization) registered to an RHN Satellite ver. 5.3.0 (or later) 2. Create a RHEL-5 KVM guest on your host & register it to the satellite 3. In the satellite webui, virtualization tab of your KVM host, see that your KVM guest is running 4. From inside your KVM host, as a root power off your KVM guest 5. After the guest system is down, run as root: # rhn-profile-sync 6. Check the the virtualization profile in the satellite webui again Actual results: See the webui shows the guest status as running. Expected results: Webui shows guest status stopped. Additional info: N/A
For this bug to reproduce, it is important to have all KVM guests powered down during execution of rhn-profile-sync.
spacewalk.git master: d544a4e6004527d9aaee60addd4ed52a6f3651ad
satellite.git SATELLITE-5.3: 5ea78350eda387aa941bf90e1ee261653fb63386
spacewalk.git master: db00ecd0fddb14f03fd8c0ffa249a467ac10c67f
satellite.git SATELLITE-5.3: f889ad068dba43a660d4d7f3a24cf5f98cd18631
Tagged & built: spacewalk-koan-0.1.11-13 rhn-virtualization-5.3.0-13
New spacewalk-koan & rhn-virtualization have been pushed into webqa.
testing procedure: sat531 + kvm host = x8664: kvm-83-105.el5_4.9 libvirt-0.6.3-20.1.el5_4 kernel-2.6.18-164.el5 koan-1.6.8-4.el5sat spacewalk-koan-0.1.11-13.el5sat rhn-virtualization-host-5.3.0-13.el5sat rhn-virtualization-common-5.3.0-13.el5sat manually (with virt-manager) stop/start/suspend kvm guest and see what happens on webUI after rhn-profile-sync on sat531 manually (with virt-manager) set mem or cpu webUI on satellite reflects all changes
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1639.html