Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionRichard 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 2Richard Homerstone
2017-10-04 11:49:00 UTC
Oops ... should have put "Always" for how reproducible
Oh, that's stupid bug.
Fixed in upstream tree by commit 949e83997906ab8dd8442f28d74c34bb5a2395ee. Thanks for your report!
Comment 5Richard 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
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
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.