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.
Bug 990405 - Auto attach action not consistent in GUI and CLI when the system have more than one product installed
Summary: Auto attach action not consistent in GUI and CLI when the system have more th...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel65
TreeView+ depends on / blocked
 
Reported: 2013-07-31 06:44 UTC by xingge
Modified: 2016-09-20 02:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-06 19:10:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
the waring screen shot. (77.70 KB, image/png)
2013-07-31 06:48 UTC, xingge
no flags Details

Description xingge 2013-07-31 06:44:53 UTC
Description of problem:
Auto attach action not persist in GUI and CLI when the system have more than one product installed

Version-Release number of selected component (if applicable):
subscription-manager-gui-1.8.14-1.el5
subscription-manager-firstboot-1.8.14-1.el5
subscription-manager-1.8.14-1.el5
python-rhsm-1.8.14-1.el5

How reproducible:
Always

Steps to Reproduce:
1.Install more than one product in one system, (cp product cert in /etc/pki/product)

2.Prepare an account that have subscriptions covered only one installed product. 

3.Use the account to register the system

4.Auto attach with CLI

5.remove all the subscriptions
#subscription-manager remove --all

5.Auto attach with GUI

Actual results:
1.After Auto attach with CLI,the subscription that cover the installed product was attached.
[root@localhost ~]# subscription-manager attach --auto
Installed Product Current Status:
Product Name: Red Hat Enterprise Linux for SAP
Status:       Not Subscribed

Product Name: JBoss Enterprise Application Platform
Status:       Not Subscribed

Product Name: Red Hat Enterprise Linux Server
Status:       Subscribed

2.After auto attach with GUI, a error window pops up said "No service level will cover all installed products."
as the attachment.

Expected results:
When auto attach with GUI, the operation should succeed.

Additional info:

Comment 1 xingge 2013-07-31 06:48:28 UTC
Created attachment 780950 [details]
the waring screen shot.

Comment 2 Devan Goodwin 2013-08-06 19:10:35 UTC
This is probably working as expected. You have three installed products and an account that only has subscriptions to cover one of them.

The GUI design/requirements for autobind after service levels were introduced was that GUI autobind should abort if there is not an SLA which matches enough subscriptions to cover all installed products. 

The GUI autobind is meant to be a highly simplified tool for the most common desired outcome. The CLI and manual GUI attaching is the fallback where you can do partial, or non-SLA autobinds.

So unfortunately this is probably not a bug, the autobind behaviour is actually meant to behave slightly different in this case.

Please reopen if I've missed anything or there is a serious problem with this.


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