Description of problem: As part of our terminology updates, subscribe is being supplanted by attach. This means we have to update auto-subscribe to be auto-attach. #: ../src/subscription_manager/gui/firstboot/rhsm_login.py:38 msgid "" "Unable to auto-subscribe, server does not support service levels. Please run " "'Subscription Manager' to manually subscribe." 1. "Unable to auto-attach, server does not support service levels. Please run Subscription Manager to manually attach subscriptions." #: ../src/subscription_manager/gui/firstboot/rhsm_login.py:96 msgid "You have opted to skip auto-subscribe." 2. "You have opted to skip auto-attach." #: ../src/subscription_manager/gui/registergui.py:465 msgid "Unable to auto-subscribe, server does not support service levels." 3. "Unable to auto-attach, server does not support service levels." #: ../src/subscription_manager/gui/data/installed.glade.h:7 msgid "Auto-subscribe" 4. "Auto-attach" Version-Release number of selected component (if applicable): subscription-manager-1.1.5-1.git
commit 07de3a24c5c7f6d7dd2c5b818d67c65d7ef47386 Author: Alex Wood <awood> Date: Fri Nov 9 15:04:43 2012 -0500 874776: Change the term 'auto-subscribe' to 'auto-attach'.
In the register module, can we update --autoattach to have a hyphen and be --auto-attach? We have a few strings as autoattach so that it matches the option, if we add a hyphen to the option then we can be consistent throughout gui and cli with hyphenation.
Comment 3 did not make it in.
Comment 3 has its very own BZ - 876340.
Created attachment 662767 [details] Unable to auto-attach
Comment on attachment 662767 [details] Unable to auto-attach Marking verified Version [root@rhel-64-server ~]# subscription-manager version server type: Red Hat Subscription Management subscription management server: 0.4.19-1 subscription-manager: 1.1.14-1.el6 python-rhsm: 1.1.7-1.el6
Created attachment 662768 [details] opted to skip
Created attachment 662769 [details] Unable to auto-attach on firstboot
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/RHBA-2013-0350.html