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 1745642 - Corosync is using link with the highest priority despite the documentation
Summary: Corosync is using link with the highest priority despite the documentation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: corosync
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Jan Friesse
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-26 14:40 UTC by Michal Mazourek
Modified: 2020-04-28 15:56 UTC (History)
3 users (show)

Fixed In Version: corosync-3.0.2-4.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 15:56:45 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
man: Fix link_mode priority description (935 bytes, patch)
2019-10-25 07:38 UTC, Jan Friesse 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1674 0 None None None 2020-04-28 15:56:55 UTC

Comment 1 Jan Friesse 2019-08-26 15:09:02 UTC 
Thank you for the report, nice catch!

We've decided to fix documentation rather than source code. Upstream patch is https://github.com/corosync/corosync/pull/500 (knet got similar one https://github.com/kronosnet/kronosnet/pull/248, but fix there is not needed, because we don't support direct knet usage by customers).
Comment 2 Patrik Hagara 2019-09-27 09:04:47 UTC 
qa_ack+, link priority manual page text will be fixed
Comment 3 Jan Friesse 2019-10-25 07:38:15 UTC 
Created attachment 1629056 [details]
man: Fix link_mode priority description

man: Fix link_mode priority description

... to match knet source code.

Signed-off-by: Jan Friesse <jfriesse>
Reviewed-by: Fabio M. Di Nitto <fdinitto>
Comment 5 Patrik Hagara 2020-01-29 12:22:12 UTC 
> [root@virt-088 ~]# rpm -q corosync
> corosync-3.0.3-2.el8.x86_64

relevant corosync.conf manual page bit:
>       link_mode
>               This specifies the Kronosnet mode, which may be passive, active, or rr (round-robin).  passive: the active link with the highest priority will be used. If one or more links share the same pri‐
>               ority  the one with the lowest link ID will be used.  active: All active links will be used simultaneously to send traffic.  link priority is ignored.  rr: Round-Robin policy. Each packet will
>               be sent to the next active link in order.
> 
>               If only one interface directive is specified, passive is automatically chosen.
> 
>               The maximum number of interface directives that is allowed with Kronosnet is 8. For other transports it is 1.


the text has been corrected (previously incorrectly stated that lowest prio link will be used):
> passive: the active link with the highest priority will be used.

marking verified in 3.0.3-2.el8
Comment 7 errata-xmlrpc 2020-04-28 15:56:45 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1674
Note You need to log in before you can comment on or make changes to this bug.