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 1016643 - [firstboot] Subscription_manager register screens missing on rhel 7 firstboot
Summary: [firstboot] Subscription_manager register screens missing on rhel 7 firstboot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Adrian Likins
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel70
TreeView+ depends on / blocked
 
Reported: 2013-10-08 13:15 UTC by Rehana
Modified: 2014-06-18 00:27 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 10:14:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
firstbootscreen (288.69 KB, image/png)
2013-10-08 13:16 UTC, Rehana 		no flags Details
firstboot screen sequence (284.04 KB, image/png)
2013-10-17 21:45 UTC, Sharath Dwaral 		no flags Details
Can't be dismissed (51.70 KB, image/png)
2013-10-29 09:21 UTC, Radek Bíba 		no flags Details
View All

Description Rehana 2013-10-08 13:15:17 UTC 
Description of problem:
Installed and configured latest rehl7 compose, observed that the firstboot screens doesnt give options to register on subscription_manager

Version-Release number of selected component (if applicable):
rpm -qa | grep subsc
subscription-manager-migration-1.10.3-1.git.0.c59a391.el7.x86_64
subscription-manager-1.10.3-1.git.0.c59a391.el7.x86_64
subscription-manager-gui-1.10.3-1.git.0.c59a391.el7.x86_64
subscription-manager-firstboot-1.10.3-1.git.0.c59a391.el7.x86_64
subscription-manager-migration-data-2.0.4-1.git.0.6bebf6f.el7.noarch
[root@localhost ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 0.8.29-1
subscription-manager: 1.10.3-1.git.0.c59a391.el7
python-rhsm: 1.10.3-1.git.0.6ac2883.el7


How reproducible:
3/3

Steps to Reproduce:
1.Launch firstboot on rhel7 machine
2.
3.

Actual results:
Observed that no subscription_manager register screens were present (PFA)

Expected results:
firstboot should have subscription_manager register screens

Additional info:
Comment 1 Rehana 2013-10-08 13:16:18 UTC 
Created attachment 809277 [details]
firstbootscreen
Comment 3 Carter Kozak 2013-10-17 14:21:16 UTC 
commit 77def35b6e10129f8a7225ca1cf155bb681bc335
Author: Devan Goodwin <dgoodwin>
Date:   Thu Oct 17 10:13:39 2013 -0300

    Fix firstboot module location on EL6.

commit 9ebbf0b4b2aaf8cfc3c5f416d2c6640566a8e253
Author: Adrian Likins <alikins>
Date:   Tue Oct 15 16:24:17 2013 -0400

    Fix firstboot issues with new firstboot.
    
    Since we now run last in firstboot, we were hitting
    a case where the threads for the subscription api
    calls were not finishing before we stop checking
    the idle loop for events (which in this case, were
    the idle source thread watcher methods).
    
    Also handle no rhn-client-tool modules being installed,
    and skip the steps that rely on them.

commit 03536843f8a6c3a47f660785d86a22cd1d434fb0
Author: Adrian Likins <alikins>
Date:   Mon Oct 14 12:13:26 2013 -0400

    Firstboot modules were installing into rhn dirs.
    
    For RHEL6, we were installing firstboot modules into
    the rhn client directories, because of interdependecies
    between the rhn and rhsm modules. Now those are removed,
    so we install to the normal firstboot module dir
    (/usr/share/firstboot/modules).
Comment 5 Sharath Dwaral 2013-10-17 21:45:42 UTC 
Created attachment 813560 [details]
firstboot screen sequence

# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.8.29-1
subscription-manager: 1.10.4-1.el7
python-rhsm: 1.10.3-1.el7


if  "/etc/sysconfig/firstboot" file exists edit "RUN_FIRSTBOOT=YES"
else  "# firstboot"  in terminal


Firstboot for RHEL7 is working. Please see attahment

VERIFIED
Comment 6 Radek Bíba 2013-10-29 09:21:05 UTC 
Created attachment 817029 [details]
Can't be dismissed

Not sure what's wrong, but here's what I see on my system. There's no way to dismiss the dialog. What gives?

If I try clicking Forward with no account information entered, I get an alert saying You must enter a login.
Comment 7 Rehana 2013-10-29 09:26:33 UTC 
Radek,

Bug https://bugzilla.redhat.com/show_bug.cgi?id=1021013 was logged to address this issue.

Hope this helps.

Rehana
Comment 8 Radek Bíba 2013-10-29 09:31:44 UTC 
Thanks Rehana, I've added myself to the cc list in the new bug.
Comment 9 Ludek Smid 2014-06-13 10:14:35 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.