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:

Username and passwords are sensitive. It would be nice for rhsm to have the ability to embed in an answer file.

This would be especially useful with a Dockerfile (example below), because one would be able to share docker files without having passwords embedded:

=================================================
# Version    1  
  
# Pull from CentOS RPM Build Image  
FROM rhel6-base  
  
MAINTAINER Scott McCarty smccarty  
  
# Update the image  
RUN subscription-manager register --username=fatherlinux --password='PASSWORD' --auto-attach  
RUN yum update -y  
RUN subscription-manager unregister
=================================================

This sounds like a good use for registration with an Activation Key which is already implemented.

However, I believe the current design for attaching subscriptions to a docker container will come from the entitlements on the host system that is running the docker container.  This was demoed by dgoodwin on https://engineering.redhat.com/trac/Entitlement/wiki/SprintReviews/EntitlementSprint76Review
Therefore no registration will be required in a Dockerfile.

NEEDINFO on dgoodwin to confirm.

What about reusing the mechanism rho has? Or is that too heavy handed for this?

Acking 7.1

Acking 7.1

Between Activation keys, and the current implentation of the docker plugin we have this feature request covered. I am closing this out.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days