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 1302775 - RHEL6-17112 - RHSM : Firstboot - Verify if user can navigate thro firstboot pages
Summary: RHEL6-17112 - RHSM : Firstboot - Verify if user can navigate thro firstboot p...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Chris Snyder
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-28 15:30 UTC by Jan Stavel
Modified: 2016-05-10 20:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 20:39:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
sequence of screens (483.89 KB, application/zip)
2016-01-28 15:30 UTC, Jan Stavel 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0797 0 normal SHIPPED_LIVE python-rhsm and subscription-manager bug fix and enhancement update 2017-01-06 16:31:50 UTC

Description Jan Stavel 2016-01-28 15:30:49 UTC 
Created attachment 1119181 [details]
sequence of screens

link to Polarion TestCase

https://polarion.engineering.redhat.com/polarion/#/project/RHEL6/workitem?id=RHEL6-17112&revision=479643
Description of problem:
User cannot see server details after he click "Back" button.

How reproducible:
Launch Firstboot and Accept the License Agreement 
------> Select "Register to Subscription-Management Service " Option 
------> Enter the server Details and click on Next 
------> Now Click on "Back" button on the page where you are supposed to enter credentials

Actual results:
There is no server details window.

Expected results:
User should be able to change server details after he decides to go back.


Additional info:

I have attached screenshots how they appeared.

Thanks,
Jan Stavel
Comment 3 John Sefler 2016-01-28 17:58:39 UTC 
Saving some time...
This bug is indeed a Regression from the RHEL6.7 version of subscription-manager-firstboot-1.14.10-1.el6.x86_64

I suspect the development of RHEL7 subscription-manager-initial-setup-addon-1.15.9-15.el7.x86_64 has introduced this regression on el6.
Comment 9 John Sefler 2016-02-03 20:21:08 UTC 
Adding more observations to this bugzilla....

Once the user has successfully gone "Forward" through all of the subscription-manager firstboot panels and successfully lands on the "Done" panel, clicking the "Back" button will navigate to the "Choose Service" panel which is effectively the module prior to subscription-manager-firstboot (which is arguably correct), then a click of the "Forward" button tries to attach subscriptions again (which is not right).

Once the user has successfully gone "Forward" through all of the subscription-manager firstboot panels and successfully lands on the "Done" panel and then click the "Forward" button to the next module (Create User)), clicking the "Back" button will navigate to the "Attaching Subscription" panel which will oscillate and then throw an error dialog stating "No available subscriptions at the current service level...".  Arguably, this is not the best panel to go back to.  It might be better to go all the way back to the first prompt of the firstboot module to enter an entitlement server hostname.
Comment 12 John Sefler 2016-03-08 20:28:16 UTC 
Verifying Version...
[root@jsefler-6 ~]# rpm -q subscription-manager-firstboot
subscription-manager-firstboot-1.16.8-4.el6.x86_64


Testing Comment 0...
VERIFIED: When the user gets to the Subscription Management registration credentials panel, clicking Back will navigate all the way back to the "Choose Service" panel where a click of Forward will re-initiate subscription-manager-firstboot and the user can enter the server information details again.  This is the newly expected Back/Forward workflow behavior (to re-start the subscription-manager-firstboot panels from the beginning).


Testing Comment 9...
VERIFIED: When the user reaches the "Done!" panel and clicks Back, then Forward into Subscription Management, the user sees the "Done!" panel again.  This is the new expected behavior.  When the user is done, the user is done!  To change their registration, he will have to use the subscription-manager CLI/GUI tools post firstboot.
Comment 14 errata-xmlrpc 2016-05-10 20:39:59 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-2016-0797.html
Note You need to log in before you can comment on or make changes to this bug.