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 732498 - Data addresses populated with class name
Summary: Data addresses populated with class name
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: matahari
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Russell Bryant
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-22 16:55 UTC by Dave Johnson
Modified: 2011-12-06 11:40 UTC (History)
3 users (show)

Fixed In Version: matahari-0.4.2-8.el6
Doc Type: Bug Fix
Doc Text:
Cause: The data address for Matahari QMF objects was inconsistent. Consequence: With some agents, the data address was the class name. In others, it was a UUID. Change: Matahari has been updated to consistently use the class name as the data address. Result: The data address across Matahari agents is now consistent.
Clone Of:
Environment:
Last Closed: 2011-12-06 11:40:12 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 Dave Johnson 2011-08-22 16:55:41 UTC
Description of problem:
===================================
With a matahari host (or network) agent connected to a broker, if I query the matahari agent class with qmf-tool, I get a list of objects with their associated data address like:

    Data Objects Returned: 1:
        Number  Data Address
        --------------------------------------------
        5       0da188af-2882-411d-84bd-c03001a5caba

However, when querying the matahari Services/Resources/Sysconfig classes, the data address is the class name.  Is that right?

    Data Objects Returned: 1:
        Number  Data Address
        ------------------------
        4       sysconfig

    Data Objects Returned: 1:
        Number  Data Address
        ------------------------
        3       Services

    Data Objects Returned: 1:
        Number  Data Address
        ------------------------
        2       Resources


Version-Release number of selected component (if applicable):
======================================================================
v0.4.2-7

How reproducible:
===================================
100%

Steps to Reproduce:
===================================
1.  install/start local matahari broker and agents
Repeat for each matahari agent
2.  set the agent as default
3.  query the class
4.  notice the data address

Comment 2 Russell Bryant 2011-08-22 23:32:49 UTC
Upstream patch committed:

https://github.com/matahari/matahari/commit/a67ab9c27873bb552222bbf1d8a0100872d3e456

Comment 4 Dave Johnson 2011-08-24 19:40:02 UTC
Good 2 go in v0.4.2-9, all agents now use the following format

    Data Objects Returned: 1:
        Number  Data Address
        ------------------------
        2       <class-name>

Comment 5 Russell Bryant 2011-11-16 21:48:10 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: The data address for Matahari QMF objects was inconsistent.
Consequence: With some agents, the data address was the class name.  In others, it was a UUID.
Change: Matahari has been updated to consistently use the class name as the data address.
Result: The data address across Matahari agents is now consistent.

Comment 6 errata-xmlrpc 2011-12-06 11:40:12 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.