Bug 1018226 - kickstart: no %packages makes the default software selection not work
Summary: kickstart: no %packages makes the default software selection not work
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: David Shea
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-10-11 13:52 UTC by Ales Kozumplik
Modified: 2014-10-20 23:01 UTC (History)
9 users (show)

Fixed In Version: anaconda-21.48.10-1.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-10-20 23:01:49 UTC
Type: Bug

Attachments (Terms of Use)
anaconda.log from the last attempt (9.50 KB, text/x-log)
2014-03-11 08:16 UTC, Ales Kozumplik
no flags Details
screrncast (4.54 MB, video/webm)
2014-03-11 08:27 UTC, Ales Kozumplik
no flags Details

Description Ales Kozumplik 2013-10-11 13:52:16 UTC
Description of problem:
20-Beta-TC1, using the kickstart below. There's notably no %packages section. When I get to the summary hub I see SOFTWARE SELECTION with the warning icon and "Gnome Desktop" status. I click it, see "Gnome Desktop" preselected, click "Done" immediately, come back to the hub, nothing has changed (i.e. still yellow icon on SOFTWARE SELECTION, can not click Begin).

All with yum payload.

*not a blocker material*.


auth --useshadow
# Install OS instead of upgrade

# Use network installation
url --url="http://download.englab.brq.redhat.com/pub/fedora/linux/development/20/x86_64/os/"
keyboard --vckeymap=us --xlayouts='us'
# System language
lang en_US.UTF-8

# Network information
# Root password
rootpw --plaintext xczdsfr4w3
# System timezone
timezone Europe/Prague --isUtc
user --name=foo --password=bar
# System bootloader configuration
bootloader --location=mbr --boot-drive=vda
# Partition clearing information
clearpart --all --initlabel

# partitioning
part / --size=2000
part /boot --size=500
part /home --size=1000
part /swap --size=1000

Comment 1 Chris Lumens 2014-02-26 20:28:46 UTC
Are you still seeing this problem with F20 final?

Comment 2 Ales Kozumplik 2014-03-11 08:15:19 UTC
Only had a chance to try today. On 0309 rawhide compose pxe boot I still get the described behavior. With the kickstart above and this command line I can not get past the main hub doing what I described in comment 0.

[anaconda root@localhost ~]# cat /proc/cmdline 
initrd=/raw_03/initrd.img inst.sshd ksdevice=bootif root=live: nokill ks=  BOOTIF=01-52-54-00-5c-a4-45 BOOT_IMAGE=/raw_03/vmlinuz

Comment 3 Ales Kozumplik 2014-03-11 08:16:00 UTC
Created attachment 873015 [details]
anaconda.log from the last attempt

Comment 4 Ales Kozumplik 2014-03-11 08:27:56 UTC
Created attachment 873019 [details]

Heck, here's a screencast of what I'm gettiong. You decide if this is or is not the expected operation please.

Comment 6 Fedora Update System 2014-10-15 13:07:43 UTC
anaconda-21.48.10-1.fc21 has been submitted as an update for Fedora 21.

Comment 7 Fedora Update System 2014-10-16 17:18:27 UTC
Package anaconda-21.48.10-1.fc21, pykickstart-1.99.63-2.fc21, python-blivet-0.61.5-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-21.48.10-1.fc21 pykickstart-1.99.63-2.fc21 python-blivet-0.61.5-1.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2014-10-20 23:01:49 UTC
anaconda-21.48.10-1.fc21, pykickstart-1.99.63-2.fc21, python-blivet-0.61.5-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.