Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 494247[details]
cluster.conf two used for testing
Description of problem:
Starting cman... [FAILED], cluster not starting
Version-Release number of selected component (if applicable):
rhel6.1 beta snapshot 4
How reproducible:
always
Steps to Reproduce:
1. setup 2 nodes, virtualized fine
2. yum -y install cman rgmanager
3. deploy cluster.conf_twonode as /etc/cluster/cluster.conf on both nodes
4. service cman start
Actual results:
Starting cman... [FAILED]
Expected results:
Starting cman... [OK]
Additional info:
Using a config with qdisk brings up the same problem, qdisk via
iscsi initiator was used here, cluster.conf_qdisk is attached.
Comment 5RHEL Program Management
2011-04-23 06:00:34 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Steven,
sorry for the noise - true, the firwall was established.
Did multiple installations to verify the behaviour, all with the new
virt-install setup here that deployed a firewall..
The cluster comes up now in both configurations, two_node as well as qdisk.
Sorry again, Christian
Created attachment 494247 [details] cluster.conf two used for testing Description of problem: Starting cman... [FAILED], cluster not starting Version-Release number of selected component (if applicable): rhel6.1 beta snapshot 4 How reproducible: always Steps to Reproduce: 1. setup 2 nodes, virtualized fine 2. yum -y install cman rgmanager 3. deploy cluster.conf_twonode as /etc/cluster/cluster.conf on both nodes 4. service cman start Actual results: Starting cman... [FAILED] Expected results: Starting cman... [OK] Additional info: Using a config with qdisk brings up the same problem, qdisk via iscsi initiator was used here, cluster.conf_qdisk is attached.