Red Hat Bugzilla – Bug 997116
"repo" options not written to /root/anaconda-ks.cfg
Last modified: 2013-08-21 16:11:41 EDT
Created attachment 786631 [details] ks-bz995526.cfg kickstart file having "repo" options Description of problem: The "repo" options from a user-defined kickstart file are not written to /root/anaconda-ks.cfg. Version-Release number of selected component (if applicable): Fedora-19-x86_64-DVD.iso $ sudo repoquery anaconda pykickstart --repoid=fedora --releasever=19 anaconda-0:19.30.13-1.fc19.x86_64 pykickstart-0:1.99.32-1.fc19.noarch How reproducible: Always. Steps to Reproduce: 1. Start installer DVD: $ qemu-kvm -m 4096 -hda f19-test-2.img -cdrom ~/xfr/fedora/F19/Fedora-19-x86_64-DVD.iso -vga std -boot menu=on 2. Append kickstart option to kernel command-line: ks=nfs:walnut.lan:/var/tmp/kickstart/ks-bz995526.cfg 3. Complete install and reboot into installed system. 4. # cat /root/anaconda-ks.cfg Actual results: No "repo" options are in /root/anaconda-ks.cfg. Expected results: All "repo" options from the input kickstart file are in /root/anaconda-ks.cfg. Additional info: The bz number in the input kickstart file is for this bug: Bug 995526 - regression: --cost ignored in kickstart file
Created attachment 786632 [details] /root/anaconda-ks.cfg without "repo" options
What evidence do you have that this is pykickstart, and not anaconda?
Why are you asking -- reassign it to libreoffice, if you want ...
This bug does not occur with F18: Bug 995526, Comment 21.
I'm asking because I enjoy wasting my time. This is almost certainly an anaconda bug, I just wanted some more data on that before I reassigned it. Thanks for continuing to be so very helpful.
There aren't any release tags for pykickstart: https://git.fedorahosted.org/cgit/pykickstart.git/log/ You got a detailed bug report, everything after is whining ...
These are the only lines in the diff between pykickstart for F18 and F19 explicitly concerning repos: $ diff -ur r1.99.22-1/ r1.99.32-1/ | grep -i repo + PYTHONPATH=. coverage report --show-missing --include='pykickstart/*' "Report-Msgid-Bugs-To: \n" -import mouse, multipath, network, partition, raid, reboot, repo, rescue, rootpw +import mouse, multipath, network, partition, raid, realm, reboot, repo, rescue, rootpw "repo": repo.F15_Repo, + "repo": repo.F15_Repo, "repo": repo.F15_Repo, + "RepoData": repo.F15_RepoData, "RepoData": repo.F15_RepoData, +- Fix a bug in logvol duplicate reporting (#924579, mhuth). (clumens) +- Make sure tests can run and report import errors (bcl) == $ sudo repoquery anaconda pykickstart --repoid=fedora --releasever=18 anaconda-0:18.37.11-1.fc18.x86_64 pykickstart-0:1.99.22-1.fc18.noarch $ sudo repoquery anaconda pykickstart --repoid=fedora --releasever=19 anaconda-0:19.30.13-1.fc19.x86_64 pykickstart-0:1.99.32-1.fc19.noarch
Steve, there's no need to make accusations of "whining" or sarcastically suggesting to re-assign to other unrelated packages. Chris was asking if you'd done more diagnostic work, because you initially assigned it to a package that, while related to the problem, was not obviously the culprit. Since you'd done such a strange thing, it seemed reasonable that maybe you'd forgotten to tell him some diagnostic task you'd done. Please do try and understand that we're trying to solve this together, and if we ask questions, it's because we think that knowing the answers for them is helpful in solving the problem.
Peter, you are scolding ...
Created attachment 786667 [details] packaging.log The attached packaging.log is the only log file that explicitly mentions a repo by name: $ grep -l updates-kern *log packaging.log
Created attachment 786669 [details] anaconda.log
*** This bug has been marked as a duplicate of bug 994940 ***