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.

Bug 1727875

Summary:	Current crypto-policies conflict with old openssh, mark that in the spec
Product:	Red Hat Enterprise Linux 8	Reporter:	Nikhil Dehadrai <ndehadra>
Component:	crypto-policies	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED ERRATA	QA Contact:	Ondrej Moriš <omoris>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.1	CC:	abokovoy, hkario, nmavrogi, omoris, rcritten, szidek, tmraz, tscherf
Target Milestone:	rc	Keywords:	Regression, Triaged
Target Release:	8.1	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	crypto-policies-20190613-2.git21ffdc8.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 22:33:24 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 Nikhil Dehadrai 2019-07-08 12:16:17 UTC

Description of problem:
sshd.service failed to start message is observed during ipa server is upgrade process when upgraded from RHEL 8.0 > RHEL 8.1

Version-Release number of selected component (if applicable):
ipa-server-4.8.0-1.module+el8.1.0+3577+202f0a51.x86_64

Steps to Reproduce:
1. Setup IPA server at RHEL 80
2. Configure latest repo for RHEL 8.1
3. Update the IPA server using command #yum -y update or #dnf -y update

Actual results:
1)During update process following message is observed:

  Upgrading        : ipa-client-4.8.0-1.module+el8.1.0+3577+202f0a51.x86_64                                    276/795 
  Running scriptlet: ipa-client-4.8.0-1.module+el8.1.0+3577+202f0a51.x86_64                                    276/795 
Job for sshd.service failed because the control process exited with error code.
See "systemctl status sshd.service" and "journalctl -xe" for details.

  Upgrading        : redhat-logos-httpd-80.8-1.el8.noarch                                                      277/795 
  Upgrading        : mod_http2-1.11.3-2.module+el8.1.0+3367+c6ef6102.x86_64                                    278/795 
  Upgrading        : httpd-2.4.37-14.module+el8.1.0+3522+6d0f6052.x86_64                                       279/795 

2) ipa server upgrade is successful



Expected results:
No error message is observed during upgrade process

Additional info:
1) [root@vm-idm-006 ~]# ipa-healthcheck   --failures-only --output-type human  is successful and no error observed
2) After upgrade is successful, the service status displayed is successful

[root@vm-idm-006 ~]# systemctl status sshd.service
● sshd.service - OpenSSH server daemon
   Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-07-08 16:47:42 IST; 50min ago
     Docs: man:sshd(8)
           man:sshd_config(5)
 Main PID: 13633 (sshd)
    Tasks: 1 (limit: 24010)
   Memory: 1.1M
   CGroup: /system.slice/sshd.service
           └─13633 /usr/sbin/sshd -D -oCiphers=aes256-gcm,chacha20-poly1305,aes256-ctr,aes256->

Jul 08 16:47:42 vm-idm-006.testrelm.test systemd[1]: Stopped OpenSSH server daemon.
Jul 08 16:47:42 vm-idm-006.testrelm.test systemd[1]: Starting OpenSSH server daemon...
Jul 08 16:47:42 vm-idm-006.testrelm.test sshd[13633]: Server listening on 0.0.0.0 port 22.
Jul 08 16:47:42 vm-idm-006.testrelm.test sshd[13633]: Server listening on :: port 22.
Jul 08 16:47:42 vm-idm-006.testrelm.test systemd[1]: Started OpenSSH server daemon.

Comment 1 Thomas Woerner 2019-07-10 08:40:53 UTC

Please add the output of "journalctl -xe". It is needed to get the exact error message for "the control process exited with error code".

Comment 13 Tomas Mraz 2019-07-23 13:28:33 UTC

I just hope the added Conflicts will fix the problem by ordering the openssh update before the crypto-policies update. But it might be that it won't do that. In that case I am unfortunately very much out of ideas how to fix it apart from reverting the change that brought the CASignatureAlgorithms configuration.

Comment 18 errata-xmlrpc 2019-11-05 22:33:24 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-2019:3644