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.

Created attachment 1605895 [details]
var log secure showing log outs.

Description of problem:
When there are open SSH connections to a RHEL 7.7 device and the run level is changed between multi-user and graphical in either direction, the SSH connections are lost.

Version-Release number of selected component (if applicable):
systemd-219-67.el7_7.1.x86_64
systemd-libs-219-67.el7_7.1.x86_64

How reproducible:
Every Time

Steps to Reproduce:
1. Spin up RHEL 7.7 system
2. open one or more SSH connections to above system.
3. change the runlevel from 5 to 3 or vice versa (systemctl isolate multi-user.target

Actual results:
Any SSH connections opened prior to runlevel change are closed

Expected results:
Any SSH connections opened prior to runlevel change should remain open

Additional info:
I'm able to re-open SSH connections after the runlevel change, but any that are open during the change are closed.

I'll attach the /var/log/secure from the rhel 7.7 VM that was created that this was replicated on. Please let me know if anything else is needed for troubleshooting this.

*** This bug has been marked as a duplicate of bug 1745199 ***