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.
+++ This bug was initially created as a clone of Bug #689128 +++
Attached patch fixes typo in code which leads to <cman transport="..." > is ignored if <totem /> XML node is present.
--- Additional comment from bubble on 2011-03-19 13:52:39 EDT ---
Created attachment 486397[details]
Fix typo
--- Additional comment from fdinitto on 2011-03-22 05:01:22 EDT ---
Hi Vladislav,
in principle the patch is correct, but cannot be applied as is and needs some more work.
<cluster>
<cman transport="...."/>
<totem transport="...."/>
In this case the patch should take care to check and either report an error that only one can be specified or eventually apply a bigger hammer and say: cman config has higher priority than totem and take appropriate action.
Basically it needs a failsafe for bad configs.
Thanks
Fabio
--- Additional comment from bubble on 2011-03-22 05:09:14 EDT ---
Will <totem transport="...."/> pass validation?
--- Additional comment from fdinitto on 2011-03-22 05:25:13 EDT ---
(In reply to comment #3)
> Will <totem transport="...."/> pass validation?
even if it doesn´t, validation can always be turned off or set to warning. It´s a matter of trying to be resilient to user errors and make sure expectations are met.
If you specify both, which one should win? etc..
--- Additional comment from bubble on 2011-03-23 09:54:42 EDT ---
Created attachment 487042[details]
2nd version of patch
Hi Fabio,
attached should be close to what you've requested.
Best,
Vladislav
--- Additional comment from fdinitto on 2011-03-23 10:58:56 EDT ---
(In reply to comment #5)
> Created attachment 487042[details]
> 2nd version of patch
>
> Hi Fabio,
>
> attached should be close to what you've requested.
>
> Best,
> Vladislav
Hi Vladislav,
at a first glance the patch looks Ok. I'll need to test it before I merge it upstream.
Thanks a lot for your work!
Fabio
--- Additional comment from fdinitto on 2011-03-28 08:12:28 EDT ---
Hi Vladislav,
there is a substantial error in the patch.
transport is a key to totem and not an object underneath totem.
So basically this will never work.
Also your patch triggers the error only when cman and totem transport are specified but it should provide always an error path when specified in totem.
Comment 1Fabio Massimo Di Nitto
2011-04-15 07:51:08 UTC
*** This bug has been marked as a duplicate of bug 695795 ***