Created attachment 634036 [details] F18 test kickstart config for Calxeda Highbank Description of problem: When performing an F18 kickstart install, I receive a backtrace (see results): AttributeError: 'YumPayload' object has no attribute 'storage' Version-Release number of selected component (if applicable): anaconda-18.19-1.fc18 How reproducible: always Steps to Reproduce: 1. Start a PXE-boot, kickstart install 2. Select the only disk drive (sda) and use all space 3. After Starting package installation, backtrace occurs Actual results: Starting package installation process Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 91, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.7/site-packages/pyanaconda/install.py", line 117, in doInstall payload.preInstall(packages=packages, groups=payload.languageGroups(ksdata.lang.lang)) File "/usr/lib/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1191, in preInstall self.checkSoftwareSelection() File "/usr/lib/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1112, in checkSoftwareSelection self._applyYumSelections() File "/usr/lib/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1098, in _applyYumSelections self.selectKernelPackage() File "/usr/lib/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1144, in selectKernelPackage kernels = self.kernelPackages File "/usr/lib/python2.7/site-packages/pyanaconda/packaging/__init__.py", line 657, in kernelPackages if self.storage.platform.armMachine is not None: AttributeError: 'YumPayload' object has no attribute 'storage' Expected results: installation completes Additional info: The kickstart config used is attached for reference.
Does updates=http://clumens.fedorapeople.org/870556.img fix this?
The update provided gets past this point in the installation before failing (due to a different issue). I believe the update provided resolves the initial problem. I will open a new BZ for the new issue.
anaconda-18.22-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.22-1.fc18
Package anaconda-18.22-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.22-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17432/anaconda-18.22-1.fc18 then log in and leave karma (feedback).
anaconda-18.23-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.23-1.fc18
anaconda-18.24-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.24-1.fc18
anaconda-18.25-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.25-1.fc18
anaconda-18.26-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.26-1.fc18
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug. (ref comment #2)