Description of problem:
When changing /etc/issue to use the \l control code (which presents the tty the getty is running on), it shows as a dash (-) instead of tty1. This behavior differs from RHEL 8 and current Fedora.

This may be due to the change to using the stdin file descriptor to determine the tty.

agetty --show-issue shows expected results (though likely just as an example for the user)

Version-Release number of selected component (if applicable):
This occurs on 9.0 and CentOS Stream 9.

How reproducible:
Always

Steps to Reproduce:
1. Modify /etc/issue and include \l...

2c2
< Kernel \r on an \m
---
> Kernel \r on an \m (\l)

2. systemctl restart getty (or logout if already on tty1 console, or switch to tty2/tty3/etc)

Actual results:
Red Hat Enterprise Linux 9.0 (Plow)
Kernel 5.14.0-70.17.1.el9_0.x86_64 on an x86_64 (-)

CentOS Stream 9
Kernel 5.14.0-119.el9.x86_64 on an x86_64 (-)

Rocky Linux 9.0 (Blue Onyx)
Kernel 5.14.0-70.17.1.el9_0.x86_64 on an x86_64 (-)

Expected results:
Running tty is shown, similar to Fedora.

Fedora Linux 36 (Thirty Six)
Kernel 5.18.7-200.fc36.x86_64 on an x86_64 (tty1)

Additional info:
This was reported at the Rocky Linux bug tracker: https://bugs.rockylinux.org/view.php?id=156 and confirmed on a RHEL 9.0 and CentOS Stream 9 system.