Bug 973528 - [RHSC] - starting/stopping/restarting gluster swift services on a node gives an incorrect message.
[RHSC] - starting/stopping/restarting gluster swift services on a node gives ...
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc (Show other bugs)
Unspecified Unspecified
high Severity high
: ---
: ---
Assigned To: Shubhendu Tripathi
Depends On:
  Show dependency treegraph
Reported: 2013-06-12 03:33 EDT by RamaKasturi
Modified: 2013-09-23 18:25 EDT (History)
6 users (show)

See Also:
Fixed In Version: bb5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-09-23 18:25:47 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 15718 None None None Never

  None (edit)
Description RamaKasturi 2013-06-12 03:33:03 EDT
Description of problem:
starting gluster swift services on a node gives an incorrect message.

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

How reproducible:

Steps to Reproduce:
1. Login to rhs console.
2. create a cluster and add nodes to it.
3. Click on the servers tab.
4. click on the gluster Swift subtab.
5. Click on StartSwift.

Actual results:
Message in the event log says that "SWIFT services started on cluster <clustername>."

Expected results:
It should say that "SWIFT services started on <hostname> on cluster <clustername>"

Additional info:
Comment 2 RamaKasturi 2013-06-12 03:36:44 EDT
Stopping swift services on a node gives the incorrect message.
Comment 3 Scott Haines 2013-09-23 18:25:47 EDT
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.


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