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 1248164

Summary: In initial-setup-addon gui, user can't correct a previous dialog
Product: Red Hat Enterprise Linux 7 Reporter: Sean Toner <stoner>
Component: subscription-managerAssignee: candlepin-bugs
Status: CLOSED DUPLICATE QA Contact: John Sefler <jsefler>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: alikins
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-30 14:04:49 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
screenshots of steps 1-3 in repro notes, and actual result none

Description Sean Toner 2015-07-29 18:37:19 UTC
Created attachment 1057380 [details]
screenshots of steps 1-3 in repro notes, and actual result

Description of problem:
=======================

If a user enters a server in which to register with, then goes to the next screen to fill in their username and password, if the user needs to make a correction on the subscription manager service details, they can't make a correction.

Even if the user clicks Done (since the Cancel button doesnt work), if they go back and try again, the GUI will go straight to the dialog to enter the username and password.

There needs to be a way to go back and allow the user to correct previously entered information.


Version-Release number of selected component (if applicable):
=============================================================


How reproducible:
=================

Always


Steps to Reproduce:
===================

1. Enter some value for the subscription manager service to use in first screen
2. Click the Done button
3. Click the Subscription Manager "button" in the main Anaconda screen (the happy face)

See screen shots
1 = register-with-intial.png
2 = click-done.png
3 = click-subscription-manager.png

Actual results:
===============

After step 3 in repro steps, observe that it skips the screen where user can fill in the subscription server and goes straight to username and password screen

See back-to-user-pw-screen.png

Expected results:
=================

The gui should take the user back to the screen to be able to re-enter the subscription registration server, and not back to the username password screen.

Ideally, there should be Back buttons in each screen (push the state for each screen on a stack, and if the user clicks Back, pop off any info for each screen...and if the user clicks the Done button, clear the stack)


Additional info:

Comment 2 Adrian Likins 2015-07-30 14:04:49 UTC

*** This bug has been marked as a duplicate of bug 1243704 ***