Description of problem: install mate desktot in smoke 11 netinstall error in configuring Version-Release number of selected component: anaconda-18.18 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.1-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.18 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 480, in execute : raise KickstartError(msg) : File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 62, in doConfiguration : ksdata.firewall.execute(storage, ksdata, instClass) : File "/usr/lib64/python2.7/threading.py", line 504, in run : self.__target(*self.__args, **self.__kwargs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run : threading.Thread.run(self, *args, **kwargs) :KickstartError: /usr/bin/firewall-offline-cmd is missing. Cannot setup firewall.
Created attachment 629191 [details] File: anaconda-tb
Created attachment 629192 [details] File: product
Created attachment 629193 [details] File: type
Created attachment 629194 [details] File: ifcfg.log
Created attachment 629195 [details] File: storage.log
Created attachment 629196 [details] File: version
Created attachment 629197 [details] File: environ
Created attachment 629198 [details] File: anaconda.log
Created attachment 629199 [details] File: syslog
Created attachment 629200 [details] File: hashmarkername
Created attachment 629201 [details] File: packaging.log
Created attachment 629202 [details] File: cmdline_file
Created attachment 629203 [details] File: release
Created attachment 629204 [details] File: program.log
smoke11 2nd bug on install Package: anaconda-18.18 OS Release: Fedora release 18
I did an install using a smoke test iso (smoke 11 - anaconda-18.18-1), selected autopartitioning and the gnome package set. The traceback appeared while "Configuring installed system" was above the installation progress bar Package: anaconda-18.18 OS Release: Fedora release 18
happened at end of Live install Package: anaconda-18.18-1.fc18.x86_64 OS Release: Fedora release 18
The repo needs to have firewalld-0.2.9-1 in it, logs show 0.2.8-1
install to HD from smoke 11 netinstall of mate-desktop worked fine after cold boot despite this error
I installed today from 18-Beta-TC6 and development tree with same error. May be some dependency problems of installer? I use kickstart minimal nobase install.
1. Boot F18 TC8 Live CD 2. Update anaconda to fix a bunch of bugs (firewalld 0.2.9 gets installed). 3. Install 4. Get above error because the image has firewalld 0.2.7 and the updated anaconda uses firewalld 0.2.9 (with the firewall-offline-cmd command). anaconda should pick up the updated packages from the live system.
Please attach the complete /tmp/anaconda-tb-* file to this bug report.
Created attachment 648677 [details] tb
Work-around is to not put in the root password during the installation, and: - start a terminal - su - chroot /mnt/sysimage - ln -s /bin/true /usr/bin/firewall-offline-cmd - close terminal - put in root password - click continue
If /mnt/sysimage/usr/bin/firewall-offline-cmd does not exist, that means /usr/bin/firewall-offline-cmd on the live cd does not exist, which means that there's a problem composing the live images. They will need logs to see what's going on with that, but I'm sure they can find them.
(In reply to comment #25) > If /mnt/sysimage/usr/bin/firewall-offline-cmd does not exist, that means > /usr/bin/firewall-offline-cmd on the live cd It exists on the liveCD's memory image, because the new anaconda pulled in the version of firewalld that supports it. It's not on the disk image that anaconda uses to dd to the destination partition. > does not exist, which means > that there's a problem composing the live images. They will need logs to > see what's going on with that, but I'm sure they can find them. It wasn't there in the live images because it didn't exist. There wasn't a new enough anaconda to need it either. The problem is that those sort of problems exist when one needs to upgrade anaconda to make it work (it failed to start as I had a wireless card).
The file absolutely must exist on the disk image, not in memory. That is how live installs work, and how they have always worked. We simply copy the exact contents of the disk image to your target drives. These sorts of issues should not be overly common because we do not change requires all that often, and certainly more frequent tree composition should help minimize the risk even more. Sorry, but I don't really see what we can do here aside from try to push people into running the absolute latest tree.