Hide Forgot
Description of problem: Trying to do a text mode ks install of F15 Alpha TC1 and I get a prompt for update disk source. For unattended installs we can't have any prompts. Is a new ks option needed? If so, a release note will be warranted. Version-Release number of selected component (if applicable): 15.19
Please attach your kickstart file and /tmp/anaconda.log. Thanks.
Created attachment 478657 [details] kickstart file
Created attachment 478658 [details] anaconda.log
Hm, those weren't as enlightening as I'd hoped. Do you remember the exact message of the dialog you're hitting?
Title: Update Disk Source You have multiple devices which could serve as sources for an update disk. Which would you like to use? sr0 vda Ok Cancel
Okay, I think I see what's going on now. Thanks.
Proposing as a blocker, as this makes automated installs no longer automated. This should hit just about everyone doing a kickstart install.
I don't think we have criteria would be impacted by fully automated installs. We'll need to work on that. In the meantime, this would *definitely* qualify as a nice to have for the Alpha in my opinion. https://fedoraproject.org/wiki/QA/ReleaseCriteria
we are working on criteria for kickstart installs, remember, jlaska. i think the email ball is in your court atm =)
Per 2011-02-18 alpha blocker meeting: #agreed 677131 - Accepted as Alpha NTH, rejected as Alpha blocker.
(In reply to comment #9) > we are working on criteria for kickstart installs, remember, jlaska. i think > the email ball is in your court atm =) I haven't settled on anything concrete from our private discussion on this, but it's still in my inbox awaiting inspiration.
Can reproduce with Alpha RC2 - please reconsider this bug as a blocker for beta, even if there's no criteria for this case yet. Required interactions in non-interactive installations are a really bad thing.
It's already been committed to the f15-branch for beta, hence the Fixed In Version: starts with a "15" instead of a "16".
*** Bug 682582 has been marked as a duplicate of this bug. ***
Discussed at 2011-03-11 blocker review meeting. This issue is fixed and available for testing in anaconda-15.21-1. The issue has been accepted as a beta blocker.
VERIFIED, I'm not seeing this in anaconda-15.24-1 images.
anaconda-15.26-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/anaconda-15.26-1.fc15
Package anaconda-15.26-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-15.26-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/anaconda-15.26-1.fc15 then log in and leave karma (feedback).
Confirmed with F-15-Beta-TC1
anaconda-15.26-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
Confirmed fixed in F15 Beta Thanks!