Bug 1020672

Summary:	[Firstboot] Invalid/Not providing credentials in the register screens of first boot send the main firstboot screen to background/minimised
Product:	Red Hat Enterprise Linux 7	Reporter:	Rehana <redakkan>
Component:	subscription-manager	Assignee:	candlepin-bugs
Status:	CLOSED WONTFIX	QA Contact:	John Sefler <jsefler>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	dgoodwin, fsharath, jmolet, skallesh, spandey
Target Milestone:	rc
Target Release:	7.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-03 15:42:13 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:
Bug Depends On:
Bug Blocks:	1005618

Description Rehana 2013-10-18 07:16:52 UTC

Description of problem:
Observed that  when no/wrong user details were given in the firstboot subscription register screen, firstboot screen was send to background/minimised 

Version-Release number of selected component (if applicable):
subscription-manager version
server type: This system is currently not registered.
subscription management server: 0.8.29-1
subscription-manager: 1.10.4-1.el7
python-rhsm: 1.10.3-1.el7


How reproducible:
4/4

Steps to Reproduce:
1.Launch firstoot
2.move to subscription register screen
3.click forward without entering the credentials --(A)
4.Issue wrong credentials and click next (B)

Actual results:
Observed that during both the cases (A) & (B) when the error message screen pops up the main First boot screen was getting minimised or send to background and after clicking "Ok" on the msg window the firstboot screen didnt come up

Expected results:
The error screen should display on the main first boot screen and after clicking "Ok" on the error message screen the control should go back to first boot screen 

Additional info:

Comment 1 Devan Goodwin 2014-01-22 13:36:33 UTC

Need to verify but I suspect this is just how firstboot behaves when an error is thrown and you're running it manually *after* logging into the system. (note that this is not how firstboot is normally meant to be used, only something we do for dev/QE testing)

I have seen this behaviour for popups after hardware profile reporting screens in firstboot, I think it's just an issue with how firstboot behaves if you're already logged in.

Need to test this but suspect this is a close wontfix or cantfix.

Comment 2 Bryan Kearney 2014-03-19 20:50:18 UTC

Moving bugs from 7.0 to 7.1

Comment 4 Bryan Kearney 2014-07-30 19:21:38 UTC

Acking 7.1

Comment 5 Devan Goodwin 2014-11-03 15:42:13 UTC

Closing as firstboot is largely unmaintained now, and we are only considering critical fixes. 

Will be addressed for 7.2 by the planned port to new anaconda installer modules. More details in comment #1.