Bug 809880

Summary:	[RFE] Run firstboot or just the installer in a user-session
Product:	[Retired] oVirt	Reporter:	Fabian Deutsch <fdeutsch>
Component:	ovirt-node	Assignee:	Fabian Deutsch <fdeutsch>
Status:	CLOSED WONTFIX	QA Contact:	bugs <bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	acathrow, hadong, iheim, jboggs, leiwang, mgoldboi, ovirt-bugs, ovirt-maint
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	node
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-24 17:03:39 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:

Description Fabian Deutsch 2012-04-04 14:45:16 UTC

Description of problem:
Currently the firstboot and the installer is run within the boot process. This is leading to a couple of bugs and dirty hacks.
E.g. it is not recommended to have an interactive boot process in the systemd era. It's also problematic to initiate a reboot from within the boot process.

A solution for this kind of problem could be, to pull the installer or the whole firstboot part into a user session, so using it as the bash for the root (or non root) account without a password.

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

How reproducible:
Always.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:
Better user experience, less bugs and hacks.

Additional info:

Comment 1 Fabian Deutsch 2014-03-24 17:03:39 UTC

The installer should be kept in the installation process, because many following services which willr ely on install-time informations.

Also anaconda does it the same way.