Bug 979324
Summary: | [RHSC] - Gluster Swift Services are not getting listed with vdsm build vdsm-4.10.2-22.5.el6rhs.x86_64 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | RamaKasturi <knarra> | ||||
Component: | rhsc | Assignee: | Timothy Asir <tjeyasin> | ||||
Status: | CLOSED ERRATA | QA Contact: | RamaKasturi <knarra> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | urgent | ||||||
Version: | 2.1 | CC: | avishwan, dtsang, knarra, mmahoney, pprakash, rhs-bugs, sabose, sdharane, shaines, ssampat | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-09-23 22:25:51 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: | |||||||
Attachments: |
|
Description
RamaKasturi
2013-06-28 08:45:55 UTC
Created attachment 766466 [details]
Attaching engine and vdsm logs.
It looks like it failed to give service list when any one of the following service is stopped. glusterd, memcached, gluster-swift-proxy, gluster-swift-container, gluster-swift-object, gluster-swift-account, smb I am suspecting "memcached" service is stopped. Can you restart the service memcached and check whether you are able to get the list of service list. Quick Fix: ~~~~~~~~~~ restart all the following services: glusterd, memcached, gluster-swift-proxy, gluster-swift-container, gluster-swift-object, gluster-swift-account, smb After doing the above quick fix, i was able to get the services listed, but all the services were listed after starting smb. I am not able to understand what is the relation between smb and swift services. Could you please explain? Verified in vdsm-4.10.2-22.6.el6rhs.x86_64 and working fine. 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-1262.html |