Bug 1470989 - Kickstart rescue command options not honored (anaconda goes interactive).
Kickstart rescue command options not honored (anaconda goes interactive).
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Radek Vykydal
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-07-14 04:35 EDT by Radek Vykydal
Modified: 2017-08-27 13:16 EDT (History)
8 users (show)

See Also:
Fixed In Version: anaconda-27.19-1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Radek Vykydal 2017-07-14 04:35:40 EDT
When specifying kickstart rescue command, installer goes interactive and asks how to proceed (same as when inst.rescue boot option is used). It should just mount the /mnt/sysimage based on rescue command options (--nomount, --romount) and run the shell on tty, which would allow eg for automatic repairs/checks of system using kickstart %pre or %post scripts.
Comment 1 Radek Vykydal 2017-07-14 05:24:41 EDT
Comment 2 Artem Bityutskiy 2017-08-18 10:43:39 EDT
Is there a chance this will get to F27?
Comment 3 Artem Bityutskiy 2017-08-18 11:07:00 EDT
FYI, I've cherry-picked the patches from the pull request on top of anaconda-26.21.10-1 and tested them. I did not test 'inst.rescue', only KS rescue.

Both 'rescue' and 'rescue --nomount' work as expected, thanks!
Comment 4 Radek Vykydal 2017-08-21 07:14:27 EDT
Yes, this will be included in F27.
Comment 5 Vit Ry 2017-08-27 13:16:13 EDT
Could you, please, cherry-pick to rhel7-branch also? :)

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