Hide Forgot
Description of problem: Freeze of vm based service is not viewable when using clustat Version-Release number of selected component (if applicable): 3.0.12-10.el6.x86_64 How reproducible: always Steps to Reproduce: 1. have a vm based service running on node intrarhev1 [root@rhev1 ~]# clustat | grep rh56 vm:rh56 intrarhev1 started From a libvirtd point of view: [root@rhev1 ~]# virsh list Id Name State ---------------------------------- 41 rh56 running 2. freeze the vm based service with the domain running [root@rhev1 ~]# clusvcadm -Z vm:rh56 Local machine freezing vm:rh56...Success The server is still running from a libvirt point of view, as expected [root@rhev1 ~]# virsh list Id Name State ---------------------------------- 41 rh56 running 3. run clustat again Actual results: [root@rhev1 ~]# clustat | grep rh56 vm:rh56 intrarhev1 started Expected results: [root@rhev1 ~]# clustat | grep rh56 vm:rh56 intrarhev1 started [Z] Additional info: The service is indeed frozen, in the sense that if you try for example to stop it you get an error: [root@rhev1 ~]# clusvcadm -s vm:rh56 Local machine stopping vm:rh56...Failure: Service is frozen Also, if you stop the guest with virsh command [root@rhev1 ~]# virsh shutdown rh56 Domain rh56 is being shutdown it is not recovered as it is indeed frozen, so not monitored by rgmanager. With the domain yet stopped, if you run [root@rhev1 ~]# clusvcadm -U vm:rh56 Local machine unfreezing vm:rh56...Success the domain is then correctly restarted by rgmanager. So all is good from a functional point of view, but it would be nice to have clustat give a notice of the frozen status of the service, as it is for "conventional" services. Gianluca
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Sincerely, I don't think it would be a big deal to solve this... I only pointed out and opened the bugzilla to improve rh el experience and do my part giving back my feedback, but for sure I won't go through my support representative for this kind of bug. Feel free to improve experience or leave it as it is now..
@Gianluca: Comment #2 is an 'automated comment' that gets put on all bugs. Right now we're finishing up the RHEL 6.1 beta phase and that comment was just indicating that your bug probably won't make RHEL 6.1 since it was filed too late to the freeze dates for the external beta. So we'll keep this open for RHEL 6.2. As a hint... any comments you see from "RHEL Product and Program Management" in bugzilla are from bots and not from a real person.
* Thu Feb 03 2011 Lon Hohberger <lhh> - 3.0.12-11 - rgmanager: Present flags in clustat output (present_flags_in_clustat_output.patch) Resolves: rhbz#634298 *** This bug has been marked as a duplicate of bug 634298 ***