Bug 1089566

Created attachment 887982 [details]
File: backtrace

Created attachment 887983 [details]
File: environ

You need to include the correct packages to support the install. Usually this means at least @standard.

Reopening.  This bug occurs on Fedora Rawhide, even though I
have specified @standard packages.

ERROR: Command failed. See logs for output.
 # ['/usr/bin/livecd-creator', '-c', '/tmp/koji-image-f22-build-7959447.ks', '-d', '-v', '--logfile', '/tmp/livecd.log', '--cache', '/tmp/koji-livecd', '-f', 'virt-p2v-1.29.2-1']
ounting directory /var/tmp/imgcreate-vgBpF9/install_root
Losetup remove /dev/loop0
 

Traceback (most recent call last):
  File "/usr/bin/livecd-creator", line 236, in <module>
     sys.exit(main())
  File "/usr/bin/livecd-creator", line 213, in main
     creator.configure()
  File "/usr/lib/python2.7/site-packages/imgcreate/creator.py", line 749, in configure
     kickstart.RPMMacroConfig(self._instroot).apply(self.ks)
  File "/usr/lib/python2.7/site-packages/imgcreate/kickstart.py", line 276, in apply
     f = open(self.path("/etc/rpm/macros.imgcreate"), "w+")
IOError :  [Errno 2] No such file or directory: '/var/tmp/imgcreate-vgBpF9/install_root/etc/rpm/macros.imgcreate'

From the log file it seems that 'rpm' is not being installed, so
perhaps it's no longer included in @standard.

I have tried a build adding rpm explicitly to the list of packages.

Really if livecd-creator needs some packages installed (eg. firewalld),
it should either include them implicitly, or give a clear error
message about what it needs.

Adding just 'rpm' (and removing @standard) was sufficient to
fix this.

However there's still a bug here in that these tools require
packages to work, and don't give a clear error message about it.
I have had to include:
 - rpm (this bug)
 - kernel (otherwise there is no boot menu)
 - firewalld (bug 884935 et al)
to get everything to work properly.

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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.

I don't think there's really much that can be done here. We can't set requirements on the package since they have nothing to do with the kickstart, and depending on the repo metadata being used in the kickstart it may or may not include the right stuff.