RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 615889 - luci cannot start an imported cluster
Summary: luci cannot start an imported cluster
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: luci
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-19 08:34 UTC by Fabio Massimo Di Nitto
Modified: 2010-11-10 22:11 UTC (History)
2 users (show)

Fixed In Version: luci-0.22.2-9.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-10 22:11:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Fabio Massimo Di Nitto 2010-07-19 08:34:48 UTC
<?xml version="1.0"?>

<cluster name="fabbione-rhel6" config_version="1" >
  <clusternodes>
    <clusternode name="rhel6-node1" votes="1" nodeid="1"/>
    <clusternode name="rhel6-node2" votes="1" nodeid="2"/>
  </clusternodes>
</cluster>

since the creating of the cluster doesn´t work yet, I created the minimal config to add a cluster to luci.

only ricci and modclusterd are running on the nodes.

luci imports the config just fine, reports that the cluster is not running.

Select both nodes in the UI and click "join the cluster", but nothing happens.

from /var/log/cluster/ no attempts to run service cman start or equivalent takes place.

Comment 1 Fabio Massimo Di Nitto 2010-07-19 08:36:15 UTC
forgot to mention, this is using the latest code from luci.git

Comment 2 Fabio Massimo Di Nitto 2010-07-19 09:11:48 UTC
Extra info:

if cman is running, it´s possible to send another start command and a stop command:

11:03:42,996 INFO  [luci.controllers.cluster] User "root" started nodes "rhel6-node1, rhel6-node2" in cluster "fabbione-rhel6"
11:04:30,885 INFO  [luci.controllers.cluster] User "root" stopped nodes "rhel6-node1, rhel6-node2" in cluster "fabbione-rhel6"

the cluster at this point is stopped, and we cannot start it anymore

Comment 3 Brian Brock 2010-07-23 17:23:48 UTC
cluster.conf created in 5.x?

Comment 4 Fabio Massimo Di Nitto 2010-07-23 17:29:04 UTC
No, all fresh for rhel6 and in this specific case it makes no difference.

The config snippet I pasted above would work anywhere.

Comment 8 releng-rhel@redhat.com 2010-11-10 22:11:59 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.