Bug 589905

Summary:	firstboot did not start on a Dell Precision T3500 system using Snapshot 2
Product:	Red Hat Enterprise Linux 6	Reporter:	Praveen Arimbrathodiyil <parimbra>
Component:	firstboot	Assignee:	Martin Gracik <mgracik>
Status:	CLOSED DUPLICATE	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	urgent	Docs Contact:
Priority:	low
Version:	6.0	CC:	aalam, dmach, llim
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-05-13 08:12:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Praveen Arimbrathodiyil 2010-05-07 09:13:06 UTC

Description of problem:
firstboot did not start after installation. I get the following line in /var/log/messages

May  7 19:30:59 savannah-test python2: abrt: detected unhandled Python exception in /usr/sbin/firstboot

Version-Release number of selected component (if applicable):
firstboot-1.110.1-1.el6.x86_64

How reproducible:

Will try it right now

Steps to Reproduce:
1. Proceed with normal installation
2.
3.
  
Actual results:
firstboot in not run and login to the system with gdm is not possible (no normal user and by default root user cannot login).

Expected results:
firstboot is run normally.

Additional info:

Comment 2 Praveen Arimbrathodiyil 2010-05-07 09:48:11 UTC

I was able to reproduce the bug on a second install.

Comment 3 Praveen Arimbrathodiyil 2010-05-07 09:49:08 UTC

It is 64 bit Workstation, installed via NFS method

Comment 4 RHEL Program Management 2010-05-07 10:16:18 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 5 Martin Gracik 2010-05-11 06:15:01 UTC

There was a bug in firstboot-1.110.1 causing this problem.
It has been fixed in firstboot-1.110.2

Comment 6 Martin Gracik 2010-05-13 08:12:00 UTC


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