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.
Request to add a new package libvirt-snmp to RHEL6.2.
The origins of the request is:
https://bugzilla.redhat.com/show_bug.cgi?id=642556
there will be dependencies on glibc, net-snmp-libs and libvirt-client,
so they should be on the approved components list.
(In reply to comment #4)
> Please clarify if this package is going to be part of a new or existing comps
> group or if this will be pulled in as a dependency.
Nothing depends on libvirt-snmp. I don't understand the comps group question, can you explain?
If nothing depends on a package, it needs to be listed in a package group (they're called comps groups) so it will actually be pulled into the tree.
From a brief look, it seems appropriate for the 'virtualization-platform' group, alongside libvirt-cim, libvirt-qpid, etc.
(In reply to comment #7)
> If nothing depends on a package, it needs to be listed in a package group
> (they're called comps groups) so it will actually be pulled into the tree.
>
> From a brief look, it seems appropriate for the 'virtualization-platform'
> group, alongside libvirt-cim, libvirt-qpid, etc.
Yes, that would be appropriate.
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/RHEA-2011-1609.html