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 1841070 - Cockpit 195 crashes with ECDSA certificate
Summary: Cockpit 195 crashes with ECDSA certificate
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 7.9
Assignee: Martin Pitt
QA Contact: Jan Ščotka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-28 09:29 UTC by Davide Principi
Modified: 2020-09-29 20:03 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-29 20:03:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github cockpit-project cockpit issues 12664 0 None closed Impossible to use a Let's Encrypt certificate with Cockpit 2020-06-30 12:30:32 UTC
Red Hat Product Errata RHBA-2020:3950 0 None None None 2020-09-29 20:03:44 UTC

Description Davide Principi 2020-05-28 09:29:38 UTC
Description of problem:

After uploading an ECDSA certificate the Cockpit service does not restart.

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

cockpit-195.6-1.el7.centos.x86_64

How reproducible:

Configure cockpit with an ECDSA certificate and restart the service.

Actual results:

The cockpit service does not start. In system journal the error:

    May 27 17:32:09 vm5.dpnet.nethesis.it systemd[1]: Starting Cockpit Web Service...
    May 27 17:32:09 vm5.dpnet.nethesis.it remotectl[6666]: remotectl: /etc/cockpit/ws-certs.d/99-nethserver.cert: No PEM-encoded private key found
    May 27 17:32:09 vm5.dpnet.nethesis.it systemd[1]: cockpit.service: control process exited, code=exited status=1


Expected results:

A new cockpit-ws process is spawned offering the new ECDSA certificate.

Additional info:

Bug originally reported here: https://github.com/NethServer/dev/issues/6183

I see the upstream Cockpit project already fixed the issue: https://github.com/cockpit-project/cockpit/pull/13074

Is it possible to backport it to Cockpit 195 in EL7?

Comment 2 Martin Pitt 2020-05-28 11:03:03 UTC
I'm happy to backport the fix. It's mostly Jan Scotka's decision whether he can fit it in QE-wise.

Comment 10 errata-xmlrpc 2020-09-29 20:03:34 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 (cockpit 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-2020:3950


Note You need to log in before you can comment on or make changes to this bug.