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.
Description of problem:
Luci website does not handle cluster member FQDN correctly.
Version-Release number of selected component (if applicable):
luci-0.22.2-14.el6_0.1.x86_64
How reproducible:
100%
Steps to Reproduce:
In this example, the cluster name is "Sun" and the member name is "mercury.solar.system.org"
1. Start luci (either on a cluster member, or a remote machine)
2. Login to the luci webpage: https://mercury.solar.system.org:8084
3. Click on the name "Sun"
4. Click on the member to get more information: "https://mercury.enterprise.bhkfirst.org:8084/cluster/Sun/mercury.solar.system.org"
Actual results:
Error 500
We're sorry but we weren't able to process this request.
From luci.log:
Error - <class 'genshi.template.eval.UndefinedError'>: {u'venus.solar.system.org': <luci.lib.cluster_status.NodeStatus instance at 0x7f37444233f8>, u'mercury.solar.system.org': <luci.lib.cluster_status.NodeStatus instance at 0x7f3744423bd8>, u'mars.solar.system.org': <luci.lib.cluster_status.NodeStatus instance at 0x7f3744423dd0>} has no member named "mercury.solar.system"
Expected results:
Detailed info about the cluster member.
Additional info:
Strange workaround fix:
Notice the very last line of the luci.log does not have the ".org" on "mercury.solar.system"
If you manually add it by attaching an extra ".org" to the URL, the detailed information works!
For example, add an extra ".org":
"https://mercury.enterprise.bhkfirst.org:8084/cluster/Sun/mercury.solar.system.org.org"
and it works.
Yes. They are the same.
Sorry about the confusion on the names above. I was trying to edit out the *.enterprise.bhkfirst.org names for security, but missed a couple.
Here is the cluster.conf:
[root@mercury luci]# cat /etc/cluster/cluster.conf
<?xml version="1.0"?>
<cluster config_version="5" name="Sun">
<fence_daemon clean_start="0" post_fail_delay="1" post_join_delay="3"/>
<clusternodes>
<clusternode name="mars.enterprise.bhkfirst.org" nodeid="1" votes="1">
<fence/>
</clusternode>
<clusternode name="venus.enterprise.bhkfirst.org" nodeid="2" votes="1">
<fence/>
</clusternode>
<clusternode name="mercury.enterprise.bhkfirst.org" nodeid="3" votes="1">
<fence/>
</clusternode>
</clusternodes>
<cman/>
<fencedevices>
<fencedevice agent="fence_bladecenter" ipaddr="misioncontrol.enterprise.bhkfirst.org" login="USERID" name="BHKBlade" passwd="PASSW0RD" power_wait="100"/>
</fencedevices>
<rm>
<failoverdomains/>
<resources/>
</rm>
</cluster>