This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 156302 - check to ensure correct num of gulm servers is not happening
check to ensure correct num of gulm servers is not happening
Status: CLOSED NEXTRELEASE
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: redhat-config-cluster (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jim Parsons
Cluster QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-28 14:33 EDT by Corey Marthaler
Modified: 2009-04-16 16:08 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-05-24 18:25:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Corey Marthaler 2005-04-28 14:33:09 EDT
Description of problem:
At save time the GUI should complain if I don't have the right number of GULM
servers (1,3,4,5) and then it should help me remedy the problem

Version-Release number of selected component (if applicable):
-42
Comment 1 Stanko Kupcevic 2005-04-28 17:45:17 EDT
Fixed in 0.9.43
Comment 2 Corey Marthaler 2005-04-28 18:13:07 EDT
It gives me the correct warning, however it then says that it saved the file
anyway. Upon inspection of the file, it didn't actually save it though, but
still confusing.
Comment 3 Stanko Kupcevic 2005-04-29 11:16:02 EDT
Fixed in 0.9.44
Comment 4 Corey Marthaler 2005-04-29 16:46:17 EDT
fix verified in -44.
Comment 5 Corey Marthaler 2005-05-24 13:00:42 EDT
There is still the case where you can have an invalid number of gulm servers and
when you try to propagate (send to cluster) you'll see this warning message but
the propagate will still be attempted. 
Comment 6 Stanko Kupcevic 2005-05-24 14:21:53 EDT
Fixed in 0.9.59
Comment 7 Corey Marthaler 2005-05-24 18:25:19 EDT
fix verififed in -60.

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