Bug 159728 - Services does not handle names with multiple words
Services does not handle names with multiple words
Status: CLOSED DUPLICATE of bug 159681
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: redhat-config-cluster (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jim Parsons
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2005-06-07 11:18 EDT by Paul Kennedy
Modified: 2015-04-19 20:46 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-07 11:38:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paul Kennedy 2005-06-07 11:18:01 EDT
Description of problem:
At the Cluster Configuration tab, creating a new service allows entering
multiple words (with spaces between words) as a name for the service. At the
Cluster Management tab, the service is displayed with no service name, while
other information (State, Owner, Previous Owner, and Restarts) varies according
to the number of words in the service name. Information gets shifted to the
right once for each word in the name. 

Version-Release number of selected component (if applicable):
system-config-cluster 0.9.67

How reproducible:
At the Cluster Configuration tab, create new services with multiple words in
their names, with spaces separating the words. For example, "three word foo".
Save and propagate the cluster configuration, and observe display at the Cluster
Management tab.

Note that running clustat displays the service names as created.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Paul Kennedy 2005-06-07 11:38:07 EDT
Inadvertently refreshed browser page for the original bug, 159681. 

*** This bug has been marked as a duplicate of 159681 ***

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