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 735419 - Agents should support multiple SRV records
Summary: Agents should support multiple SRV records
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: matahari
Version: 6.2
Hardware: All
OS: All
unspecified
medium
Target Milestone: rc
: ---
Assignee: Russell Bryant
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On: 735417
Blocks: 743047
TreeView+ depends on / blocked
 
Reported: 2011-09-02 15:26 UTC by Russell Bryant
Modified: 2011-12-06 11:42 UTC (History)
2 users (show)

Fixed In Version: matahari-0.4.4-1.el6
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Cause: When specifying a broker to connect to, one could only specify a hostname or IP address. Consequence: Providing a list of brokers to connect to that can be updated dynamically was not possible. Change: Mataari now supports querying for DNS SRV records to determine the broker, or list of brokers to attempt to connect to. Result: Administrators can now use DNS SRV to control where Matahari agents connect to.
Clone Of: 735417
Environment:
Last Closed: 2011-12-06 11:42:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1569 0 normal SHIPPED_LIVE matahari bug fix and enhancement update 2011-12-06 00:39:06 UTC

Description Russell Bryant 2011-09-02 15:26:16 UTC 
+++ This bug was initially created as a clone of Bug #735417 +++

Description of problem:

The current DNS SRV support in Matahari agents only works as expected if there is only a single DNS SRV record.  They do not support connection attempts to more than one.


Version-Release number of selected component (if applicable):

0.4.3
Comment 2 Russell Bryant 2011-09-07 19:16:42 UTC 
This has been addressed in a few upstream commits, starting with this one:

https://github.com/matahari/matahari/commit/cc2edca53821c5b1d0401076e298322b166d8106
Comment 4 Dave Johnson 2011-09-13 13:56:34 UTC 
good 2 go in v0.4.2-2

[root@agent ~]# /usr/sbin/matahari-qmf-networkd -vvv
mh_hostname: Got hostname: agent.test.com
mh_dnsdomainname: Got dnsdomainname: 'test.com'
mh_connect: SRV query successful: _matahari._tcp.test.com
mh_connect: Trying: amqp:tcp:broker1.test.com:49000
mh_connect: Trying: amqp:tcp:broker2.test.com:49000
mh_connect: Trying: amqp:tcp:broker.test.com:49000
mh_os_uuid: Got uuid: ce76da54cbe7c1d9ed1d44ce00000023
mh_hostname: Got hostname: agent.test.com
mh_hostname: Got hostname: agent.test.com
mh_os_uuid: Got uuid: ce76da54cbe7c1d9ed1d44ce00000023
mainloop_add_qmf: Added source: 1
run: Starting agent mainloop
Comment 5 Russell Bryant 2011-11-16 22:12:19 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: When specifying a broker to connect to, one could only specify a hostname or IP address.
Consequence: Providing a list of brokers to connect to that can be updated dynamically was not possible.
Change: Mataari now supports querying for DNS SRV records to determine the broker, or list of brokers to attempt to connect to.
Result: Administrators can now use DNS SRV to control where Matahari agents connect to.
Comment 6 errata-xmlrpc 2011-12-06 11:42:48 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.

http://rhn.redhat.com/errata/RHBA-2011-1569.html
Note You need to log in before you can comment on or make changes to this bug.