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:
For admin users of command line interface to subscription-manager, it would be nice to have a "--auto" option to the subscribe module. It would function exactly like the existing "--autosubscribe" option for register.
Wanted:
# subscription-manager subscribe --auto
As an admin user, I find myself preferring to register and using the list module to see what subscriptions are available to me and what products I have installed before wanting to subscribe. Then if I want to autosubscribe, my only option is to unregister and re-register with --autosubscribe. Alternatively it would be nicer/faster for me to call subscribe --auto.
Version-Release number of selected component (if applicable):
Currently subscription-manager-0.95.2
added. it should output results identical to those of register --autosubscribe.
available in master and rhel6 branches, should be in versions 0.95.4 and 0.96.2
This feature works as expected:
[root@jmolet-vm3 ~]# subscription-manager subscribe --help
Usage: subscription-manager subscribe [OPTIONS]
subscribe
Options:
-h, --help show this help message and exit
--debug=DEBUG debug level
--proxy=PROXY_URL proxy url in the form of proxy_hostname:proxy_port
--proxyuser=PROXY_USER
user for http proxy with basic authentication
--proxypassword=PROXY_PASSWORD
password for http proxy with basic authentication
--pool=POOL subscription pool id
--auto automatically subscribe this system to
compatible subscriptions.
[root@jmolet-vm3 ~]# subscription-manager subscribe --auto
Installed Products:
Large File Support Bits - Subscribed
Awesome OS Scalable Filesystem Bits - Subscribed
Awesome OS Modifier Bits - Subscribed
Awesome OS Developer Bits - Not Subscribed
Awesome OS Developer Basic - Not Subscribed
Shared Storage Bits - Subscribed
Multiplier Product Bits - Not Subscribed
Awesome OS for S390X Bits - Not Subscribed
Management Bits - Subscribed
Awesome OS Premium Architecture Bits - Not Subscribed
Awesome OS Server Bits - Subscribed
Load Balancing Bits - Subscribed
Clustering Bits - Subscribed
Awesome OS Workstation Bits - Subscribed
[root@jmolet-vm3 ~]# rhsm-version
subscription-manager-gnome-0.95.3-1.git.10.4ec14b7.el6.x86_64
subscription-manager-0.95.3-1.git.10.4ec14b7.el6.x86_64
subscription-manager-firstboot-0.95.3-1.git.10.4ec14b7.el6.x86_64
python-rhsm-0.95.3-1.git.0.4d0ef8e.el6.noarch
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHEA-2011-0611.html