Bug 924261
Summary: | cfg service: When shutdown cannot be processed immediately, it's not possible to repeat | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Friesse <jfriesse> | ||||||
Component: | corosync | Assignee: | Jan Friesse <jfriesse> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | high | ||||||||
Version: | 6.4 | CC: | cluster-maint, jkortus, sdake, slevine, sradvan | ||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | corosync-1.4.1-16.el6 | Doc Type: | Bug Fix | ||||||
Doc Text: |
Cause:
In very rare conditions, running corosync-cfgtool -H.
Consequence:
corosync-cfgtool -H returns error 6 (CS_ERR_TRY_AGAIN). When command is called again, error (CS_ERR_EXISTS) is always returned.
Fix:
corosync-cfgtool is changed to automatically retry (so no longer error 6 - CS_ERR_TRY_AGAIN). cfg library now allows call shutdown function multiple times.
Result:
corosync-cfgtool -H works all time.
|
Story Points: | --- | ||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2013-11-21 04:33:37 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 907894, 960054 | ||||||||
Attachments: |
|
Description
Jan Friesse
2013-03-21 12:57:12 UTC
Created attachment 713830 [details]
Proposed patch - part 2 - cfgtool Retry shutdown on CS_ERR_TRY_AGAIN
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-1531.html |