Bug 1498462 - agetty not parsing /etc/os-release correctly when processing /etc/issue
Summary: agetty not parsing /etc/os-release correctly when processing /etc/issue
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: util-linux
Version: 7.4
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: Radka Brychtova
URL:
Whiteboard:
Depends On:
Blocks: 1465901
TreeView+ depends on / blocked
 
Reported: 2017-10-04 11:47 UTC by Richard Homerstone
Modified: 2018-04-10 17:28 UTC (History)
2 users (show)

Fixed In Version: util-linux-2.23.2-44.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 17:27:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0936 0 None None None 2018-04-10 17:28:01 UTC

Description Richard Homerstone 2017-10-04 11:47:06 UTC
Description of problem:
When using the \S{VARIABLE} option in /etc/issue an incorrect value is returned by agetty

Version-Release number of selected component (if applicable):
agetty from util-linux 2.23.2

How reproducible:


Steps to Reproduce:
1. Set /etc/issue to the following configuration
Session: \l
\S{NAME} \S{VERSION}
(IP=\4{eth1})
2. Restart/Reload getty related services
#systemctl restart getty
3. Observe virtual console(s) on tty1

Actual results:
Session: tty1
Red hat Enterprise Linux Server _ID="7.4
(IP=10.xxx.xxx.xxx)

Expected results:
Session: tty1
Red hat Enterprise Linux Server 7.4 (Maipo)
(IP=10.xxx.xxx.xxx)

Additional info:
It appears to be the matching of the variable names when parsing /etc/os-release as it appears to be finding VERSION="7.4 (Maipo)" and then finding VERSION_ID="7.4" ... If you switch the order of these in the os-release file so that VERSION_ID comes before VERSION the expected behaviour is observed.

Comment 2 Richard Homerstone 2017-10-04 11:49:00 UTC
Oops ... should have put "Always" for how reproducible

Comment 3 Karel Zak 2017-10-05 09:14:34 UTC
Oh, that's stupid bug. 

Fixed in upstream tree by commit 949e83997906ab8dd8442f28d74c34bb5a2395ee. Thanks for your report!

Comment 5 Richard Homerstone 2017-10-05 09:49:43 UTC
Thanks for the speedy response and having looked at the fix I can see that instead of changing the order of the variables in /etc/os-release I can simply change the variable used in /etc/issue from \S{VERSION} to \{VERSION=} and this will work both now and when the patch comes through.

Keep up the great work

Comment 11 errata-xmlrpc 2018-04-10 17:27:15 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0936


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