Bug 1782652 - not generate any warning for the deprecated auth and authconfig kickstart command.
Summary: not generate any warning for the deprecated auth and authconfig kickstart com...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.1
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: 8.0
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-12 02:49 UTC by Masahiro Matsuya
Modified: 2020-11-16 10:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-16 10:30:36 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Masahiro Matsuya 2019-12-12 02:49:52 UTC
Description of problem:

auth (or authconfig) kickstart command was deprecated in RHEL8 [1].
RHEL8 installation automatically uses authconfig command provided by authselect package. It's good. 

But, the deprecation message of the auth (or authconfig) command should be logged into anywhere. Other deprecated commands (like "install") generate KickstartDeprecationWarning in /tmp/anaconda.log.


[1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/performing_an_advanced_rhel_installation/kickstart-commands-and-options-reference_installing-rhel-as-an-experienced-user

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 8.1

How reproducible:
Always

Steps to Reproduce:
1. Install RHEL8 with a kickstart including authconfig command.

Actual results:
It doesn't generate any warning for the deprecated auth (or authconfig) command.

Expected results:
It generates a warning for the deprecated auth (or authconfig) command.

Additional info:
inst.ksstrict doesn't affect for auth (or authconfig) command.

Comment 6 Jiri Konecny 2020-11-10 10:41:40 UTC
Hello Masahiro Matsuya,

could you please verify if this bug is fixed in the RHEL-8.3?


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