Version-Release number of selected component: livecd-tools-17.15-1.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 cmdline: /usr/bin/python -tt /usr/bin/livecd-creator --config=/home/james/Documents/admin/exams/practical/f17/jah-localbuild.ks --fslabel=JAH-live-F17-x86_64 --cache=/var/cache/live-f17-x86_64 -d -v --logfile=build.log kernel: 3.6.6-1.fc17.x86_64 backtrace: :kickstart.py:244:apply:IOError: [Errno 2] No such file or directory: '/var/tmp/imgcreate-pUZpAA/install_root/etc/inittab' : :Traceback (most recent call last): : File "/usr/bin/livecd-creator", line 221, in <module> : sys.exit(main()) : File "/usr/bin/livecd-creator", line 205, in main : creator.configure() : File "/usr/lib/python2.7/site-packages/imgcreate/creator.py", line 728, in configure : kickstart.XConfig(self._instroot).apply(ksh.xconfig) : File "/usr/lib/python2.7/site-packages/imgcreate/kickstart.py", line 244, in apply : f = open(self.path("/etc/inittab"), "rw+") :IOError: [Errno 2] No such file or directory: '/var/tmp/imgcreate-pUZpAA/install_root/etc/inittab' : :Local variables in innermost frame: :self: <imgcreate.kickstart.XConfig object at 0x160b490> :ksxconfig: <pykickstart.commands.xconfig.F14_XConfig object at 0x14e5f50>
Created attachment 642386 [details] File: executable
Created attachment 642388 [details] File: environ
Created attachment 642390 [details] File: dso_list
Created attachment 642393 [details] File: smolt_data
Created attachment 642395 [details] File: core_backtrace
I also encounter this with livecd-tools-18.12-2.fc18
The workaround is to turn off SELinux temporarily ("setenforce 0") on the host before building the image, and then turn it back on again ("setenforce 1") afterwards. It happens because SELinux somehow prevents scripts inside the image from adding new groups to /etc/group. That causes several RPM installation scripts to fail, and so quite a few RPMs don't get installed. One of these is initscripts, so /etc/inittab is missing, and kickstart.py gives up when it tries to write to that file. Note that /etc/inittab is deprecated, and so kickstart.py shouldn't really be writing to it anyway, but this is just a symptom of an earlier problem. The proper solution is to make sure that SELinux doesn't clobber the writes to /etc/group; after that, the RPM installations should succeed and everything in the garden will be lovely.
(In reply to comment #7) That did the trick, thanks for pointing it out!
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.