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:
Sep  2 19:20:57 virt-009 corosync[3150]: [TOTEM ] A new membership (10.34.71.9:140) was formed. Members joined: 2 4294967295
Sep  2 19:20:57 virt-009 corosync[3150]: [QUORUM] This node is within the primary component and will provide service.
Sep  2 19:20:57 virt-009 corosync[3150]: [QUORUM] Members[3]: 1 2 -1

Note the -1 in the output instead of the big ID. In our discussion Honza suggested filing this RFE and ask for making the output adjustable (%u, %d, %x).

Version-Release number of selected component (if applicable):
corosync-2.3.4-7.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. set large node ids in corosync.conf
2. start corosync cluster
3.

Actual results:
-1 in output for big IDs

Expected results:
output as per user request (%u, %d or %x).

Additional info:

Just as reminder, main reasonable for this bug is to walk thru source code of corosync/tools and replace nodeid output modifier with macro, so it will be evident WHAT is nodeid.

It may also make sense to consider moving nodeid to defined type instead of int (type may be macro, so no real change, but makes clear distinction what is nodeid).

PR for corosync master branch can be found as a https://github.com/corosync/corosync/pull/491. Implemented is only compile-time part, because runtime change turned out to be way over.

I'm closing this bug for RHEL 7, because change is quite massive and potentially risky, but it should get into RHEL 8 with next rebase.