RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2000140 - inst.ks.device Anaconda option not working in spite of the non inst. prefixed options removal in RHEL 9
Summary: inst.ks.device Anaconda option not working in spite of the non inst. prefixed...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: anaconda
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Radek Vykydal
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 2003009
TreeView+ depends on / blocked
 
Reported: 2021-09-01 13:44 UTC by Radek Vykydal
Modified: 2021-12-07 21:23 UTC (History)
6 users (show)

Fixed In Version: anaconda-34.25.0.16-1.el9_b
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2003009 (view as bug list)
Environment:
Last Closed: 2021-12-07 21:20:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-95884 0 None None None 2021-09-01 13:45:00 UTC
Red Hat Issue Tracker RTT-3720 0 None None None 2021-09-09 16:43:44 UTC
Red Hat Issue Tracker RTT-3721 0 None None None 2021-09-09 16:43:51 UTC

Description Radek Vykydal 2021-09-01 13:44:02 UTC 
Description of problem:

In RHEL 9 Anaconda boot options without inst. prefix were removed/replaced with options starting with inst. prefix (bug 1947376).
For the ksdevice option it means the change from "ksdevice" to "inst.ks.device", which also the warning on installation terminal says:

<snip>
Starting installer, one moment...
12:49:45.
############## Installer errors encountered during boot ##############
'ksdevice' is deprecated and has been removed.
All usage of Anaconda boot arguments without 'inst.' prefix was removed. Please use inst.ks.device instead.
</snip>

Much of the functionality of the ksdevice boot option has been replaced in RHEL7 and RHEL8. AFAIK the only remaining valid use is documented in "Performing an advanced RHEL installation" guide, section "B.4.1. network (optional)":

"If the --device= option is missing on the first use of the network command, the value of the ksdevice= Anaconda boot option is used, if available. Note that this is considered deprecated behavior; in most cases, you should always specify a --device= for every network command. "


Version-Release number of selected component (if applicable):

RHEL 9.0 Beta, for example
RHEL-9.0.0-20210831.d.4
anaconda-34.25.0.15-1.el9


How reproducible:

Always


Steps to Reproduce:

Run installation on a system with two network devices, eg ens3 and ens7, using these boot options:

ip=ens3:dhcp inst.ks.device=ens7

and this network command in kickstart:

network --bootproto dhcp

Which means:
- ens3 device should be configured and activated in initramfs
- ens7 device in stage 2 based on kickstart configuration using inst.ks.device option to supply missing --device option of the network command


Actual results:

The kickstart configuration is not applied to the device ens7.


Expected results:

The kickstart configuration is applied to the device ens7.


Additional info:

Replacing the inst.ks.device with ksdevice the result is as expected.

There is a question if we really also want to remove support for ksdevice (non-prefixed) option in RHEL 9.0 because inst.ks.device has never been a valid boot option - unlike some other options where for some time (RHEL 8?) both inst. prefixed and non-prefixed version worked, for example "repo" and "inst.repo".

Upstream PR adding support for inst.ks.device and removing support for ksdevice:
https://github.com/rhinstaller/anaconda/pull/3587
Comment 6 Radek Vykydal 2021-09-07 13:22:57 UTC 
https://github.com/rhinstaller/anaconda/pull/3591
Comment 8 Jan Stodola 2021-09-07 13:25:10 UTC 
The same problem should be fixed in RHEL-8, see bug 2001913.
Comment 10 Jan Stodola 2021-09-08 09:04:03 UTC 
The change from comment 6 was successfully tested by QE - the warning is not shown any more.
Comment 16 Jan Stodola 2021-09-23 08:10:51 UTC 
anaconda-34.25.0.16-1.el9_b is present in compose RHEL-9.0.0-20210922.6, moving to VERIFIED.
Note You need to log in before you can comment on or make changes to this bug.