Bug 488714 - Enabling (according to failover domain rules) a frozen service results in a unusable failed+frozen service
Summary: Enabling (according to failover domain rules) a frozen service results in a u...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rgmanager
Version: 5.3
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-05 12:33 UTC by Juanjo Villaplana
Modified: 2009-09-02 11:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-02 11:04:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
fix (463 bytes, patch)
2009-03-06 19:27 UTC, Lon Hohberger
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2009:1339 0 normal SHIPPED_LIVE Low: rgmanager security, bug fix, and enhancement update 2009-09-01 10:42:29 UTC

Description Juanjo Villaplana 2009-03-05 12:33:29 UTC
Description of problem:

Trying to enable a service that has been frozen (using the -F flag --enable according to failover domain rules---) returns an error and leaves the service in 'failed [Z]' state.

After that, it is not possible to disable/enable/stop/restart/unfreeze this service.


Version-Release number of selected component (if applicable):

rgmanager-2.0.46-1.el5


How reproducible:

Always


Steps to Reproduce:

# hostname -s
clu107
# clustat | grep disc
 service:disc                   clu107-gst                     started
# clusvcadm -d disc
Local machine disabling service:disc...Success
# clustat | grep disc
 service:disc                   (clu107-gst)                   disabled
# clusvcadm -Z disc
Local machine freezing service:disc...Success
# clustat | grep disc
 service:disc                   (clu107-gst)                   disabled   [Z]
# clusvcadm -e disc
Local machine trying to enable service:disc...Failure: Service is frozen
# clustat | grep disc
 service:disc                   (clu107-gst)                   disabled   [Z]

# clusvcadm -e disc -F
Local machine trying to enable service:disc...Failure
# clustat | grep disc
 service:disc                   (clu107-gst)                   failed     [Z]

# clusvcadm -d disc   
Local machine disabling service:disc...Failure: Service is frozen
# clusvcadm -e disc
Local machine trying to enable service:disc...Failure: Service is frozen
# clusvcadm -s disc
Local machine stopping service:disc...Failure: Service is frozen
# clusvcadm -R disc
Local machine trying to restart service:disc...Failure: Service is frozen
# clusvcadm -U disc
Local machine unfreezing service:disc...Temporary failure; try again
# clustat | grep disc
 service:disc                   (clu107-gst)                   failed     [Z]


Actual results:

The service 'disc' gets unusable.


Expected results:

The service should get back to 'disabled [Z]', and then to 'disabled'


Additional info:

Comment 1 Juanjo Villaplana 2009-03-05 13:11:52 UTC
I tried to restart cman, qdiskd and rgmanager on node clu107. cman and qdiskd restarted OK, but rgmanager got stuck on start.

Tried to stop only rgmanager on the three remaining nodes but it get stuck on stop.

After a power reset (reboot was unable to restart the system) all nodes were able to start all cluster modules, the service 'disc' was not frozen and all seems to work fine.

Comment 2 Lon Hohberger 2009-03-06 19:20:13 UTC
It should immediately fail (and not try to enable) if frozen.

Comment 3 Lon Hohberger 2009-03-06 19:27:12 UTC
Created attachment 334342 [details]
fix

Comment 7 errata-xmlrpc 2009-09-02 11:04:56 UTC
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/RHSA-2009-1339.html


Note You need to log in before you can comment on or make changes to this bug.