Bug 1670604 - Configuring SSL certs should enable certmonger service
Summary: Configuring SSL certs should enable certmonger service
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.9.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.11.0
Assignee: Joe Vlcek
QA Contact: Sudhir Mallamprabhakara
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-29 21:35 UTC by Brant Evans
Modified: 2019-12-12 13:35 UTC (History)
5 users (show)

Fixed In Version: 5.11.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-12 13:35:22 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:4199 0 None None None 2019-12-12 13:35:36 UTC

Description Brant Evans 2019-01-29 21:35:39 UTC
Description of problem:
Using appliance_console_cli to configure SSL certificates uses certmonger, but does not enable the service to start after a reboot

Version-Release number of selected component (if applicable):
cfme-5.9.7.2-1.el7cf.x86_64

How reproducible:
always

Steps to Reproduce:
(Requires an IDM server to be setup and configured)

1. Configure an appliance as normal so evmserverd processes start

     appliance_console_cli \
       --region=1 \
       --internal \
       --username=root \
       --password=redhat \
       --key \
       --dbdisk=/dev/vdb


2. Use appliance_console_cli to join the appliance to an IPA domain

     appliance_console_cli \
       --ipaserver=idm.example.com \
       --ipaprincipal=admin \
       --ipapassword=redhat

3. Use appliance_console_cli to setup SSL Certs

     appliance_console_cli \
       --ca=ipa \
       --http-cert

4. View the status of the certmonger service (it will be "active (running)"

     systemctl status certmonger

5. Reboot the appliance

6. Login and view the status of the certmonger service (it will be "inactive (dead)")


Actual results:
certmonger service is not running after rebooting the appliance.

Expected results:
certmonger service is running after rebooting the appliance.

Additional info:
This can be worked around by issuing the command "systemctl enable certmonger" after step 3.

Comment 2 Joe Vlcek 2019-02-07 20:14:40 UTC
Brant suggested that the solution for this issue may simply be to issue an enable on the certmonger service after starting it.

e.g.
% systemctl status certmonger
● certmonger.service - Certificate monitoring and PKI enrollment
   Loaded: loaded (/usr/lib/systemd/system/certmonger.service; disabled; vendor preset: disabled)

# Note it is "disabled"


% systemctl status certmonger
● certmonger.service - Certificate monitoring and PKI enrollment
   Loaded: loaded (/usr/lib/systemd/system/certmonger.service; enabled; vendor preset: disabled)

# Note it is "enabled" and will restart on reboot.

Comment 4 CFME Bot 2019-02-27 21:57:44 UTC
New commit detected on ManageIQ/manageiq-appliance_console/master:

https://github.com/ManageIQ/manageiq-appliance_console/commit/99af5e1f7182c35d147270dd2824022c4be3f9e8
commit 99af5e1f7182c35d147270dd2824022c4be3f9e8
Author:     Joe VLcek <jvlcek>
AuthorDate: Tue Feb 12 12:08:52 2019 -0500
Commit:     Joe VLcek <jvlcek>
CommitDate: Tue Feb 12 12:08:52 2019 -0500

    Enable certmonger to restart on reboot

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1670604

 lib/manageiq/appliance_console/certificate_authority.rb | 16 +-
 spec/certificate_authority_spec.rb | 56 +-
 2 files changed, 69 insertions(+), 3 deletions(-)

Comment 5 Antonin Pagac 2019-06-19 13:11:24 UTC
Appliance version: 5.11.0.8.

When installing certs, there is a message:

creating ssl certificates
configuring apache to use new certs
enabling certmonger to start on reboot

The certmonger service is running after appliance reboot.

Comment 8 errata-xmlrpc 2019-12-12 13:35:22 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:4199


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