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.
The same issue described in comment 0 against the latest rhel7 containers also occurs in the latest rhel6 containers as shown here....
[root@jsefler-rhel7 ~]# docker run -i -t --rm registry.access.redhat.com/rhel6:latest /bin/bash
[root@e6d1b449d87a /]#
[root@e6d1b449d87a /]# rpm -q subscription-manager
subscription-manager-1.20.10-7.el6.x86_64
[root@e6d1b449d87a /]#
[root@e6d1b449d87a /]# truncate --size=0 /var/log/rhsm/rhsm.log
[root@e6d1b449d87a /]#
[root@e6d1b449d87a /]# subscription-manager status
subscription-manager is disabled when running inside a container. Please refer to your host system for subscription management.
[root@e6d1b449d87a /]# cat /var/log/rhsm/rhsm.log
2018-07-12 15:37:42,633 [DEBUG] subscription-manager:17:MainThread @https.py:61 - Using m2crypto wrappers to provide httplib and ssl
2018-07-12 15:37:42,762 [DEBUG] subscription-manager:17:MainThread @dbus_interface.py:37 - self.has_main_loop=False
2018-07-12 15:37:42,762 [DEBUG] subscription-manager:17:MainThread @dbus_interface.py:53 - Unable to connect to dbus
2018-07-12 15:37:42,762 [ERROR] subscription-manager:17:MainThread @dbus_interface.py:54 - org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/subscription_manager/dbus_interface.py", line 40, in __init__
self.bus = dbus.SystemBus()
File "/usr/lib/python2.6/site-packages/dbus/_dbus.py", line 202, in __new__
private=private)
File "/usr/lib/python2.6/site-packages/dbus/_dbus.py", line 108, in __new__
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 125, in __new__
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
2018-07-12 15:37:42,799 [DEBUG] subscription-manager:17:MainThread @ga_loader.py:91 - ga_loader GaImporterGtk2
2018-07-12 15:37:42,800 [DEBUG] subscription-manager:17:MainThread @plugins.py:569 - loaded plugin modules: []
2018-07-12 15:37:42,800 [DEBUG] subscription-manager:17:MainThread @plugins.py:570 - loaded plugins: {}
2018-07-12 15:37:42,800 [DEBUG] subscription-manager:17:MainThread @identity.py:137 - Loading consumer info from identity certificates.
2018-07-12 15:37:42,800 [DEBUG] subscription-manager:17:MainThread @identity.py:148 - Reload of consumer identity cert /etc/pki/consumer/cert.pem raised an exception with msg: [Errno 2] No such file or directory: '/etc/pki/consumer/key.pem'
[root@e6d1b449d87a /]#
[root@e6d1b449d87a /]# exit
exit
[root@jsefler-rhel7 ~]#
Red Hat Enterprise Linux 6 is in the Production 3 Phase. This bug is not URGENT hence does not meet the inclusion criteria for Production Phase 3. As such this bug is being closed WONTFIX.
If you believe this to be in error, please reopen the bug with justification for why this bug should be urgent priority and severity.