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.
Description of problem:
When in container mode, attempts to start the subscription-manager-gui (from the terminal or the Desktop). The "subscription-manager is disabled when running inside a container. Please refer to your host system for subscription management." should be presented.
Version-Release number of selected component (if applicable):
[root@jsefler-6 ~]# rpm -q subscription-manager-gui
subscription-manager-gui-1.12.4-1.el6.x86_64
How reproducible:
Steps to Reproduce:
[root@jsefler-6 ~]# mkdir /etc/rhsm-host
[root@jsefler-6 ~]# subscription-manager-gui
Actual results:
the gui starts
Expected results:
subscription-manager is disabled when running inside a container. Please refer to your host system for subscription management.
Additional info:
Version:
# subscription-manager version
server type: This system is currently not registered.
subscription management server: 0.9.21-1
subscription management rules: 5.11
subscription-manager: 1.12.11-1.el6
python-rhsm: 1.12.5-1.el6
Verification:
# mkdir /etc/rhsm-host
# subscription-manager-gui
GUI starts up
# service rhsmcertd status
rhsmcertd (pid 13496) is running...
# mkdir /etc/rhsm-host
# subscription-manager version
subscription-manager is disabled when running inside a container. Please refer to your host system for subscription management.
# service rhsmcertd status
rhsmcertd (pid 13496) is running...
rhsmcertd shold be disabled
Verification FAILED.
While less than ideal, subscription-manager can run inside containers (it is presently disabled). As it can be useful (especially for testing) these tools (including the cli) should not be disabled inside containers.
The solution to this will come when we create a package including only the subscription-manager yum plugin. That package can then be added to containers as necessary.
See for additional details: https://github.com/candlepin/subscription-manager/pull/995#issuecomment-49183764