Description of problem: Trying to do a network install from kickstart. Using additional repos. Before this I was informed that package X is not available (even though it was in the repos I added from kickstart), do I want to continue? I said yes. I did this for several more packages before getting this error report. Thanks Version-Release number of selected component: anaconda-18.35 Additional info: libreport version: 2.0.18 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.9-4.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.35 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/logging/__init__.py", line 328, in getMessage : msg = msg % self.args : File "/usr/lib64/python2.7/logging/__init__.py", line 464, in format : record.message = record.getMessage() : File "/usr/lib64/python2.7/logging/__init__.py", line 723, in format : return fmt.format(record) : File "/usr/lib64/python2.7/logging/handlers.py", line 791, in emit : msg = self.format(record) + '\000' : File "/usr/lib64/python2.7/site-packages/pyanaconda/anaconda_log.py", line 114, in emit : SysLogHandler.emit(self, record) : File "/usr/lib64/python2.7/logging/__init__.py", line 748, in handle : self.emit(record) : File "/usr/lib64/python2.7/logging/__init__.py", line 1308, in callHandlers : hdlr.handle(record) : File "/usr/lib64/python2.7/logging/__init__.py", line 1268, in handle : self.callHandlers(record) : File "/usr/lib64/python2.7/logging/__init__.py", line 1258, in _log : self.handle(record) : File "/usr/lib64/python2.7/logging/__init__.py", line 1184, in critical : self._log(CRITICAL, msg, args, **kwargs) : File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3656, in selectGroup : self.logger.critical(_('Group %s does have %u conditional packages, which may get installed.'), count_cond_test) : File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1056, in _selectYumGroup : self._yum.selectGroup(groupid, group_package_types=pkg_types) : File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1179, in _applyYumSelections : self._selectYumGroup(group.name, default=default, optional=optional) : File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1209, in checkSoftwareSelection : self._applyYumSelections() : File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1294, in preInstall : self.checkSoftwareSelection() : File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 125, in doInstall : payload.preInstall(packages=packages, groups=payload.languageGroups(ksdata.lang.lang)) : 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) :TypeError: not enough arguments for format string
Created attachment 659439 [details] File: release
Created attachment 659440 [details] File: product
Created attachment 659441 [details] File: type
Created attachment 659442 [details] File: storage.log
Created attachment 659443 [details] File: version
Created attachment 659444 [details] File: environ
Created attachment 659445 [details] File: executable
Created attachment 659446 [details] File: anaconda.log
Created attachment 659447 [details] File: syslog
Created attachment 659448 [details] File: hashmarkername
Created attachment 659449 [details] File: packaging.log
Created attachment 659450 [details] File: cmdline_file
Created attachment 659451 [details] File: ks.cfg
Created attachment 659452 [details] File: anaconda-tb
Created attachment 659453 [details] File: program.log
This looks like the error line in question: self.logger.critical(_('Group %s does have %u conditional packages, which may get installed.'), count_cond_test)
Looking at the anaconda.log did show me a problem with the custom repos I added. 10:12:21,785 WARN yum.YumBase: Bad id for repo: Adobe Flash, byte = 5 10:12:21,785 WARN yum.YumBase: Bad id for repo: RPM Fusion for Fedora 18 - Free, byte = 3 10:12:21,786 WARN yum.YumBase: Bad id for repo: RPM Fusion for Fedora 18 - Nonfree, byte = 3 Byte 3 and 5 show a space. I went into the ks.cfg and replaced all " " with "_" and I no longer get the missing package errors. But I still get the same traceback. Should I file a bug about the space issue? That used to work with F17, I'm using the same kickstarts.
Same error happens with Test Compose 1 as well.
http://yum.baseurl.org/gitweb?p=yum.git;a=commitdiff;h=4687ffe Fixed upstream, will build -48.fc18 if necessary.
*** Bug 889608 has been marked as a duplicate of this bug. ***
*** Bug 895741 has been marked as a duplicate of this bug. ***
yum-3.4.3-48.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/yum-3.4.3-48.fc18
Package yum-3.4.3-48.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 yum-3.4.3-48.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-0959/yum-3.4.3-48.fc18 then log in and leave karma (feedback).
yum-3.4.3-48.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
I would like to add this issue as a commonbug Here is a IRC report on #fedora-devel <bakers> Did the options for including/excluding packages in kickstart change? I can't add a package in kickstart. I get errors that the package doesn't exist when I KNOW it does <bakers> Here is my file: [...] <bakers> I'm just trying to install postfix at the time of install <kwizart> bakers, try not to have space in "repo' names <bakers> kwizart: repo --name="Fedora 18 - x86_64" you mean that? <kwizart> there is a yum issue related to that ... <bakers> kwizart: SOB! I think that was it! <bakers> I've been working on this for a week! The workaround is to remove space from the name of the repo. There is already a kickstart bug listed as commonbug and it should be rather common for kickstart users to list several additional repositories including fedora ones for their installs. Also the experienced error doesn't explicitly point to the solution as if the problem when the kickstart was parsed.
*** Bug 904702 has been marked as a duplicate of this bug. ***