Red Hat Bugzilla – Bug 1315261
Going from signed ca/server cert back to self signed cert causes an issue with ssl and foreman (ERF12-2749)
Last modified: 2018-02-21 11:54:37 EST
I am moving this bug to sat-future. Several things are being done to resolve the certs issues.
First, https://access.redhat.com/solutions/2263671 has been updated by GSS and Engineering. This now contains the correct steps resolve the certs issues which are found.
Second, https://bugzilla.redhat.com/show_bug.cgi?id=1218251 is going to be fixed as part of 6.2. This is one of the main causes of putting the machines into the incorrect state.
Third, this bug will be tracked to
to bake into the installer a way to reset the certificates fully.
Fixing the title
Created redmine issue http://projects.theforeman.org/issues/18322 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18322 has been resolved.
As per the updated steps from Toledo on IRC:
<Toledo> but yeah to verify the bug do the following
<Toledo> install with custom certs and make sure it looks good
<Toledo> then run
<Toledo> satellite-installer --scenario satellite --certs-reset -v
<Toledo> then see if they go back to default
So, I retested this bug and :
1. I don't encounter such exception mentioned in the description or my previous comment 8.
2. Satellite is accessible from browser, no certs issues
3. Certs Reset command is successful.
4. Certs settings under UI Settings page are correct:
Changing the state to Verified !
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/RHSA-2018:0336