Bug 660754 - Anaconda ignores "interactive" option
Summary: Anaconda ignores "interactive" option
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 14
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-07 17:51 UTC by Andrew McNabb
Modified: 2011-01-05 16:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-04 15:08:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Andrew McNabb 2010-12-07 17:51:42 UTC
Starting with Fedora 14, the "interactive" option in kickstart files seems to be ignored.  It also seems to have been removed from the wiki documentation on July 16, 2010.  However, I haven't found any mention of a deliberate removal in the release notes.  The "interactive" option was a really helpful way to do interactive installations as quickly as possible, with timezones, repositories, and other options pre-specified.  If this feature disappeared unintentionally, then this is a bug report; if it was intentionally removed, then this is a feature request. :)

Comment 1 Chris Lumens 2010-12-07 18:12:18 UTC
The interactive command presented us with no end of troubles, so it has been removed.  Sorry.

Comment 2 Andrew McNabb 2010-12-07 19:27:10 UTC
There should at least be an error if "interactive" is specified in the kickstart file.  I had a hard drive that was erroneously reformatted because Anaconda proceeded through the drive initialization without asking for confirmation.  I think "interactive" should cause a fatal error in the installer.

Comment 3 Chris Lumens 2010-12-07 19:38:30 UTC
It's currently marked as deprecated, which means it has no effect but does not raise an error.  You will see a warning about it in the logs though.  Once a release or two has passed, I will remove it entirely and then it will cause installation to halt.

Comment 4 Andrew McNabb 2010-12-07 20:03:02 UTC
Hopefully not too many people will lose data in the meantime.

Comment 5 Axel Thimm 2011-01-04 14:16:19 UTC
The online documentation has not been updated to reflect the missing "interactive" support, in fact it isn't even tagged as deprecated.
http://docs.fedoraproject.org/en-US/Fedora/14/html/Installation_Guide/s1-kickstart2-options.html

Furthermore "deprecated" means that the functionality is still there, but will be removed in the future, not that it already has been removed! The current state is not "deprecated", but "removed".

Let me add that "interactive" was extremely helpful. End users and admins could see and edit what the kickstart produced and this can even help disclose more core bugs than a botched install which needs to be analysed post-mortem. And no, neither is autostep a sane substitute (I do want to check whether my %packages selection makes sense and possible add something during that install), nor can one argue that the setup is still interactive, as it will stop if anaconda is missing something - users/admins want to check the default values, too.

Thankfully with RHEL6 interactive is still alive, but I wonder how many bug reports would be raised if this change had been made to RHEL6? And whether RHEL7 will need a resurrection of interactive?

This change may ease on the anaconda development team resources, but lengthens the development cycles for large scale deployments of Fedora. I actually make extensive use of non-interactive cobbler driven site deployments, but for getting at that productive stage I do use "interactive" a lot. IMHO it is a regression and should be fixed instead of removed. Please reconsider adding interactive back to Fedora's anaconda. Thanks!

Comment 6 Chris Lumens 2011-01-04 15:08:45 UTC
Sorry, but the interactive command will not be coming back.  It simply makes too much of a mess in everything in anaconda and in my opinion never should have been added in the first place.  It breaks most every assumption we can make about what a kickstart installation really means.  This is most certainly not a regression.

Comment 7 Andrew McNabb 2011-01-04 22:24:11 UTC
I'm personally not asking to bring it back.  Please just make it die with an error instead of potentially destroying data.

Comment 8 Chris Lumens 2011-01-05 16:47:21 UTC
> I'm personally not asking to bring it back.  Please just make it die with an
> error instead of potentially destroying data.

Yeah, this is a good point.  I have marked it as such in pykickstart so this will be taken care of for F15.


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