Bug 874776 - String Updates: Auto-subscribe -> Auto-attach
Summary: String Updates: Auto-subscribe -> Auto-attach
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Shwetha Kallesh
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: 771481 840993
TreeView+ depends on / blocked
 
Reported: 2012-11-08 20:11 UTC by Matt Reid
Modified: 2013-02-21 09:00 UTC (History)
4 users (show)

Fixed In Version: subscription-manager-1.1.7-1
Doc Type: Release Note
Doc Text:
In Red Hat Enterprise Linux 6.4, several strings have been renamed in Subscription Manager: subscribe was renamed to attach auto-subscribe was renamed to auto-attach unsubscribe was renamed to remove consumer was renamed to system or unit
Clone Of:
Environment:
Last Closed: 2013-02-21 09:00:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Unable to auto-attach (112.17 KB, image/png)
2012-12-13 07:58 UTC, Shwetha Kallesh
no flags Details
opted to skip (109.20 KB, image/png)
2012-12-13 08:04 UTC, Shwetha Kallesh
no flags Details
Unable to auto-attach on firstboot (113.86 KB, image/png)
2012-12-13 08:05 UTC, Shwetha Kallesh
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0350 0 normal SHIPPED_LIVE subscription-manager bug fix and enhancement update 2013-02-20 20:53:35 UTC

Description Matt Reid 2012-11-08 20:11:49 UTC
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

Comment 2 Adrian Likins 2012-11-12 17:17:50 UTC
commit 07de3a24c5c7f6d7dd2c5b818d67c65d7ef47386
Author: Alex Wood <awood>
Date:   Fri Nov 9 15:04:43 2012 -0500

    874776: Change the term 'auto-subscribe' to 'auto-attach'.

Comment 3 Matt Reid 2012-11-13 19:47:11 UTC
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 4 Bryan Kearney 2012-11-13 20:58:26 UTC
Comment 3 did not make it in.

Comment 5 Matt Reid 2012-11-13 21:43:09 UTC
Comment 3 has its very own BZ - 876340.

Comment 7 Shwetha Kallesh 2012-12-13 07:58:41 UTC
Created attachment 662767 [details]
Unable to auto-attach

Comment 8 Shwetha Kallesh 2012-12-13 08:02:01 UTC
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

Comment 9 Shwetha Kallesh 2012-12-13 08:04:11 UTC
Created attachment 662768 [details]
opted to skip

Comment 10 Shwetha Kallesh 2012-12-13 08:05:28 UTC
Created attachment 662769 [details]
Unable to auto-attach on firstboot

Comment 12 errata-xmlrpc 2013-02-21 09:00:13 UTC
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


Note You need to log in before you can comment on or make changes to this bug.