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.

Bug 1268028

Summary: checking "Manually attach subscriptions after registration" does not work in initial-setup
Product: Red Hat Enterprise Linux 7 Reporter: John Sefler <jsefler>
Component: subscription-managerAssignee: candlepin-bugs
Status: CLOSED ERRATA QA Contact: John Sefler <jsefler>
Severity: high Docs Contact:
Priority: high    
Version: 7.2CC: alikins, crog, csnyder, redakkan, skallesh
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 11:51:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
auto-attach
none
Register with auto-attach none

Description John Sefler 2015-10-01 15:31:45 UTC 
Description of problem:
If I check the "Manually attach subscriptions after registration" box during the registration process within initial-setup, the workflow behaves as though I did not check it.  Auto-binding appears to proceed and can lead me to a Select Service Level panel that has no navigation buttons displayed and I get stuck. 

Version-Release number of selected component (if applicable):
[root@jsefler-7 ~]# rpm -q subscription-manager-initial-setup-addon
subscription-manager-initial-setup-addon-1.15.9-13.el7.x86_64


How reproducible:


Steps to Reproduce:
1. With two product certs installed that are not covered by a subscription with the same service level, start initial-setup and proceed to register to a valid account and choose "Manually attach subscriptions after registration" checkbox.


Actual results:


Expected results:
registration should complete without attempting to attach any subscriptions.

Additional info:
Comment 2 Adrian Likins 2015-10-01 16:02:31 UTC 
upstream pr at https://github.com/candlepin/subscription-manager/pull/1313
Comment 3 Adrian Likins 2015-10-01 16:09:06 UTC 
Notes on the wacky behavior:

After register, we were async starting 'finished' _and_ moving to the select sla screen (and it's long pre/startup). So gui would momentarily show the done screen, pause the progress bars, (and for initial-setup, hide the nav buttons) while the select sla screen was also showing a now paused progress bar and eventually whatever the results of select slas pre() was (potentially including error info). Basically, it finished, and then started select sla anyway.
Comment 4 Rehana 2015-10-01 17:15:25 UTC 
Scenario 2 :

RHSM registration from initial-setup with "auto-attach" ( without checking "Manually attach subscriptions after registration ) is taking to "Confirm Subscriptions" page again and again

steps:

1.Launch initial setup
2.Register client to stage environment with OUT checking the option "Manually attach subscriptions after registration"
3.Message " Error subscribing unit" is displayed (PFA) 

Expected result:

system should get successfully registered and subscribed to the available matching subscription.
Comment 5 Rehana 2015-10-01 17:16:00 UTC 
Created attachment 1079211 [details]
auto-attach
Comment 6 Chris Snyder 2015-10-01 17:47:14 UTC 
commit 576c025b34c9d80b14031c2fb40719998eec541a
Author: Adrian Likins <alikins>
Date:   Thu Oct 1 11:55:05 2015 -0400

    1268028: Fix skipped auto attach in registergui
    
    When using initial-setup to register a system, if the
    'Manually attach subscriptions after registration' option
    was selected in the credentials page, the gui would
    start the select sla screen before starting the 'done'
    process. So the done screen could be shown, then a
    now paused progress bar, then eventually the results of
    the select sla screens startup.
    
    Fix is just to either finish, or start select sla, not
    both.
Comment 11 Shwetha Kallesh 2015-10-12 08:26:28 UTC 
Created attachment 1081906 [details]
Register with auto-attach

Marking verified as register with and without auto-attach on a system with installed products that are not covered by same service-level thro initial-setup is working fine.


[root@dhcp35-36 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 2.0.6-1
subscription management rules: 5.17
subscription-manager: 1.15.9-14.el7
python-rhsm: 1.15.4-5.el7
Comment 12 errata-xmlrpc 2015-11-19 11:51:11 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.

https://rhn.redhat.com/errata/RHBA-2015-2122.html