Bug 1000405
Summary: | glusterd : 'service glusterd status' gave error 'glusterd dead but subsys locked' | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Rachana Patel <racpatel> |
Component: | glusterd | Assignee: | Nagaprasad Sathyanarayana <nsathyan> |
Status: | CLOSED EOL | QA Contact: | storage-qa-internal <storage-qa-internal> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 2.1 | CC: | amukherj, lmohanty, mzywusko, rcyriac, rhs-bugs, smohan, vbellur |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | glusterd | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-03 17:21:47 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: |
Description
Rachana Patel
2013-08-23 11:54:06 UTC
It should be ensured that after a package update, the system is returned with all the processes in the *same state* as it was before the update. It is the sysadmin's prerogative on what state a process must be on the system. If a running process is a blocker to an update due to some reason, any of the following methods should be used 1) Print out an error message that the process has to be stopped before update, and prevent the update from happening 2) If it is safe to stop the process during the update process, the process may be stopped, but it should be ensured that the process is brought back to the original state after the update Upstream 3.6 bug for this is https://bugzilla.redhat.com/show_bug.cgi?id=1113543. Upstream patch is http://review.gluster.org/#/c/8855 (for master) and http://review.gluster.org/#/c/8857/ (for 3.6) Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/ If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release. |