Bug 751438

Summary: AOS spin defaults to graphical.target.
Product: [Fedora] Fedora Reporter: Oliver Henshaw <oliver.henshaw>
Component: spin-kickstartsAssignee: Jeroen van Meeuwen <vanmeeuwen+fedora>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: bruno, kevin, maxamillion, vanmeeuwen+fedora
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 17:18:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
make kickstart xconfig work properly with systemd none

Description Oliver Henshaw 2011-11-04 17:58:30 UTC
Description of problem:

The fedora-aos kickstart creates a system that tries to boot to graphical.target. It should be booting to multi-user.target. This happens when calling image-creator with --releasever 15 and --releasever 16.

Version-Release number of selected component (if applicable):
livecd-tools-15.8-1.fc15.x86_64
fedora-kickstarts-0.15.6-1.fc15.noarch


Steps to Reproduce:

1. image-creator -c /usr/share/spin-kickstarts/fedora-aos.ks
2. mount the resulting image
3. ll mountpoint/etc/systemd/system/default.target
  
Actual results:

mountpoint/etc/systemd/system/default.target -> /lib/systemd/system/graphical.target

Expected results:

mountpoint/etc/systemd/system/default.target -> /lib/systemd/system/multi-user.target

Comment 1 Oliver Henshaw 2011-12-02 19:03:03 UTC
So the reason for this is that livecd/imgcreate/kickstart.py:XConfig() still thinks it's dealing with sysv init. The reason no-one noticed that livecd-tools needed updating is that systemd defaults to the run-level-5 equivalent, whereas sysv used to default to run-level-3.

Comment 2 Oliver Henshaw 2011-12-02 19:17:00 UTC
Created attachment 539742 [details]
make kickstart xconfig work properly with systemd

Here's a basic patch that makes livecd-tools do the right thing with-regard-to xconfig in the kickstart file.

I'm not sure if this is the best approach to take, arguably systemd default.target should point to multi-user.target by default and XConfig should change the link if xconfig is specified, following the behaviour of fedora when sysv ruled the roost.

Comment 3 Bruno Wolff III 2011-12-02 20:29:29 UTC
It might be worth looking at the work Adam did in Bug 739446 which hasn't been incorporated into live images yet.

Comment 4 Oliver Henshaw 2012-04-23 18:27:40 UTC
Whoops, thought I'd replied to this.

This isn't related to the livesys* scripts, it's due to livecd-creator/image-creator/appliance-creator thinking we still live in an inittab world when trying to respect the xconfig kickstart command.

This is already fixed in anaconda - http://git.fedorahosted.org/git/?p=anaconda.git;a=commit;h=a56d705e00d62336f732f28382b129caee706845

Boxgrinder has a work-around - https://github.com/boxgrinder/boxgrinder-build/commit/4744768a2b5e08fce53b372558bbd246efd96dfe - and apparently nobody else is using appliance-creator?

Comment 5 Fedora End Of Life 2012-08-06 20:04:17 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Fedora End Of Life 2012-08-06 20:04:17 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Oliver Henshaw 2012-08-08 12:44:48 UTC
Doesn't appear to have changed in git.

Comment 8 Fedora End Of Life 2013-07-04 05:58:14 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Fedora End Of Life 2013-08-01 17:18:07 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.