Bug 615926 - luci does not handle qdisk / cman config correctly
Summary: luci does not handle qdisk / cman config correctly
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: luci (Show other bugs)
(Show other bugs)
Version: 6.0
Hardware: All Linux
low
medium
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
: 616380 (view as bug list)
Depends On:
Blocks: 620679
TreeView+ depends on / blocked
 
Reported: 2010-07-19 09:41 UTC by Fabio Massimo Di Nitto
Modified: 2016-04-26 14:05 UTC (History)
4 users (show)

Fixed In Version: luci-0.22.2-12.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 620679 (view as bug list)
Environment:
Last Closed: 2010-11-10 22:12:03 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Fabio Massimo Di Nitto 2010-07-19 09:41:13 UTC
always latest code from git.

import a very basic cluster config:

<?xml version="1.0"?>
<cluster>
 <clusternodes>
  <clusternode name="rhel6-node1" nodeid="1" votes="1"/>
  <clusternode name="rhel6-node2" nodeid="2" votes="1"/>
 </clusternodes>
</cluster>

luci automatically adds:

<cman expected_votes="1" two_node="1"/>

that is OK.

Later in the process add a qdisk device by label with one ping heuristic.

the cman section should go away and the whole cluster restarted (including qdiskd).

Instead, the cman section is still there and qdiskd is not running.

Comment 3 Fabio Massimo Di Nitto 2010-07-26 14:32:09 UTC
*** Bug 616380 has been marked as a duplicate of this bug. ***

Comment 7 Ryan McCabe 2010-08-03 06:16:07 UTC
Fixed in git commit d0fab117082f7081b5d9675fbddf0945fe0763a4

Comment 8 Fabio Massimo Di Nitto 2010-08-03 09:12:24 UTC
the commit seems to fix the issue

Comment 26 releng-rhel@redhat.com 2010-11-10 22:12:03 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


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