Bug 458462

Summary:	sles11 firstboot correctly shuts down when aborted, but doesn't start next time
Product:	[openSUSE] openSUSE 11.2	Reporter:	Tony Ernst <tee>
Component:	YaST2	Assignee:	Jiří Suchomel <jsuchome>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P4 - Low	CC:	drahn, erik.jacobson, gp, susedev
Version:	unspecified
Target Milestone:	Alpha 0
Hardware:	Other
OS:	SLES 11
See Also:	http://bugworks.engr.sgi.com/query.cgi/990727
Whiteboard:
Found By:	Third Party Developer/Partner	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Tony Ernst 2008-12-11 21:54:32 UTC

Not urgent.
When you trigger yast2-firstboot to fire, now by touching
/var/lib/YaST2/reconfig_system
firstboot fires properly.

However, if you abort, firstboot does not start again next time.

Therefore, if you abort the questions once, you're not asked again on the
next boot.  I believe this is different than how it worked in the past.

not a show-stopper by any means.

Some may see it as a feature to avoid a firstboot loop if, for some reason,
they don't know the answers/can't answer the firstboot questions.
It seems likely this isn't the intended result.  

For exmaple, someone could decide not to accept the license
The system would shut down, but then boot up next time.

Comment 1 Jiří Suchomel 2008-12-16 19:55:43 UTC

Strange, actually the file should be removed when the firstboot stage correctly finishes... do you have the log files from such session?

Comment 2 Erik Jacobson 2008-12-16 19:57:45 UTC

I'll re-produce this and attach some logs and such.
Let me know if you'd like to see anything else.
(Changing NEEDINFO to me)

Comment 3 Jiří Suchomel 2008-12-17 08:22:42 UTC

I tried to reproduce it. When I refused to accept the licence, the (virtual) machine was shut down and on next start, firstboot configuration started again...

Comment 4 Jiří Suchomel 2009-01-21 09:13:55 UTC

Erik, did you have time to test it again?

Comment 5 Erik Jacobson 2009-01-21 15:25:32 UTC

I'm happy to report that I can't make this happen with newer sles11 versions.

While testing this, I ran in to 458465 again btw.  That is, I tested by
taking a configured system... touching /var/lib/YaST2/reconfig_system, and
rebooting.

When I got to network setup, the settings that were supposed to be for an
ethernet device again showed up as a bridge.  So I had to delete that stuff
and re-enter the proper values.

Disclosure: I didn't make it all the way through firstboot because it hung up
in SuSEconfig.  However, it hung up in one of our own scripts.  In any case,
this specific bug is tested and is fine and this SuSEconfig issue is ours.
Since this bug tested fine, I don't think I need to reserve time on a different
system just to verify this last piece so I didn't.

Comment 6 Jiří Suchomel 2009-01-29 06:59:08 UTC

If I understand it correctly, this report shows not a firstboot bug.