Bug 1002737

Summary: initial-setup-graphical.service does not run - TypeError: Argument 1 does not allow None as a value
Product: [Fedora] Fedora Reporter: Paul Whalen <pwhalen>
Component: initial-setupAssignee: Vratislav Podzimek <vpodzime>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: jreznik, kparal, robatino, satellitgo, vpodzime
Target Milestone: ---   
Target Release: ---   
Hardware: arm   
OS: Unspecified   
Whiteboard: AcceptedBlocker
Fixed In Version: anaconda-20.17-1.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-19 02:38: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:
Bug Depends On:    
Bug Blocks: 245418, 980649    

Description Paul Whalen 2013-08-29 20:26:31 UTC
Description of problem: 

When booting a freshly installed ARM image the system boots to a login screen rather than displaying the initial configuration. As a result, no user is created and no password set.


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


How reproducible:

Everytime.

Steps to Reproduce:
1. Download a f20 alpha disk image, boot using HW or QEMU


Actual results:
System boots to a login screen. 

Expected results:
System boots to initial-setup-graphical


Additional info:

systemctl status initial-setup-graphical reports:
..
Dec 31 19:00:44 localhost.localdomain xinit[296]: self.entry_hostname.set_text(value)
Dec 31 19:00:44 localhost.localdomain xinit[296]: TypeError: Argument 1 does not allow None as a value
..

Comment 1 Kamil Páral 2013-09-04 16:59:38 UTC
Discussed at 2013-09-04 blocker review meeting [1]. This is accepted as an Alpha blocker, because it violates the following F20 alpha release criterion for ARM images with a graphical desktop: "A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility." [2]

[1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-09-04/
[2] https://fedoraproject.org/wiki/Fedora_20_Alpha_Release_Criteria#Expected_installed_system_boot_behavior

Comment 2 Vratislav Podzimek 2013-09-05 10:31:34 UTC
Patch posted to anaconda-patches.

Comment 3 Fedora Update System 2013-09-06 22:43:16 UTC
anaconda-20.12-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.12-1.fc20

Comment 4 Fedora Update System 2013-09-07 17:03:54 UTC
Package anaconda-20.12-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-20.12-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-16040/anaconda-20.12-1.fc20
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-09-10 00:12:06 UTC
anaconda-20.13-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.13-1.fc20

Comment 6 Fedora Update System 2013-09-10 19:49:16 UTC
anaconda-20.14-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.14-1.fc20

Comment 7 Fedora Update System 2013-09-12 01:04:16 UTC
anaconda-20.15-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.15-1.fc20

Comment 8 Paul Whalen 2013-09-12 14:38:31 UTC
This is still failing in RC2:

Sep 12 10:29:37 localhost xinit[306]: if ifcfg.get("MASTER"):
Sep 12 10:29:37 localhost xinit[306]: AttributeError: 'NoneType' object has no attribute 'get'

Comment 9 Jaroslav Reznik 2013-09-12 16:37:20 UTC
That seems like another check is missing as the initial reported one is fixed.

Comment 10 Fedora Update System 2013-09-14 01:03:52 UTC
anaconda-20.16-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.16-1.fc20

Comment 11 Fedora Update System 2013-09-14 17:45:23 UTC
Package anaconda-20.16-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-20.16-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-16735/anaconda-20.16-1.fc20
then log in and leave karma (feedback).

Comment 12 Fedora Update System 2013-09-16 17:46:28 UTC
anaconda-20.17-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.17-1.fc20

Comment 13 Paul Whalen 2013-09-16 19:12:42 UTC
verified fixed in anaconda-20.17-1.fc20

Comment 14 Fedora Update System 2013-09-19 02:38:49 UTC
anaconda-20.17-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.