Bug 1907781

Summary:	ttyrun-getty@ and serial-getty@ conflict with each other
Product:	Red Hat Enterprise Linux 8	Reporter:	Renaud Métrich <rmetrich>
Component:	s390utils	Assignee:	Dan Horák <dhorak>
Status:	CLOSED ERRATA	QA Contact:	Vilém Maršík <vmarsik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.3	CC:	dhorak, rvr
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0
Hardware:	s390x
OS:	All
Whiteboard:
Fixed In Version:	s390utils-2.16.0-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-09 20:04:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Renaud Métrich 2020-12-15 08:27:21 UTC

Description of problem:

Starting/Enabling ttyrun-getty@ and serial-getty@ should be mutually exclusive, since the instance cannot be shared, e.g.

ttyrun-getty@hvc0 and serial-getty@hv0 cannot connect simultaneously.

I would suggest adding the following stanza to ttyrun-getty@.service unit:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
[Unit]
Conflicts=serial-getty@%i.service
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Version-Release number of selected component (if applicable):

s390utils-iucvterm-1.23.0-46.el7.s390x


How reproducible:

Always

Steps to Reproduce:
1. Start ttyrun-getty@hvc0

  # systemctl start ttyrun-getty@hvc0

Actual results:

serial-getty@hvc0 fails

Comment 1 Dan Horák 2020-12-15 08:35:24 UTC

Renaud, could you open an upstream ticket for it at https://github.com/ibm-s390-tools/s390-tools, please? I assume it's not a RHEL-7 specific issue.

Comment 2 Dan Horák 2021-01-04 13:55:42 UTC

reported upstream as https://github.com/ibm-s390-tools/s390-tools/issues/105

Comment 3 Dan Horák 2021-03-16 16:29:00 UTC

fixed in https://github.com/ibm-s390-linux/s390-tools/commit/d23558f1d1b8268f1ebcb4c05c692a89f2a433c0

Comment 4 Vilém Maršík 2021-07-20 16:01:00 UTC

Hangs on HW on my s390x machine, I probably miss the correct HW configuration. At least the config line is there:
# grep Conflicts /usr/lib/systemd/system/ttyrun-getty@.service
Conflicts=serial-getty@%i.service
# rpm -q s390utils-iucvterm
s390utils-iucvterm-2.16.0-1.el8.s390x

Comment 5 Vilém Maršík 2021-07-20 16:02:07 UTC

To the timeout:
Jul 20 11:58:17 s390x-kvm-009.lab.eng.rdu2.redhat.com systemd[1]: dev-hvc0.device: Job dev-hvc0.device/start timed out.
Jul 20 11:58:17 s390x-kvm-009.lab.eng.rdu2.redhat.com systemd[1]: Timed out waiting for device dev-hvc0.device.

Comment 6 Vilém Maršík 2021-08-06 14:11:41 UTC

Hello, seems to have stuck in Modified, can you shift it to ON_QA?

Comment 9 Vilém Maršík 2021-08-09 23:24:49 UTC

RHEL-8.5.0-20210804.d.3 still fixed in the means of Comment #4:
# rpm -q s390utils-iucvterm
s390utils-iucvterm-2.16.0-2.el8.s390x
# grep Conflicts /usr/lib/systemd/system/ttyrun-getty@.service
Conflicts=serial-getty@%i.service

Comment 11 errata-xmlrpc 2021-11-09 20:04:21 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 (s390utils bug fix and enhancement update), 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-2021:4506