Project

General

Profile

Actions

Bug #15538

closed

The installer should check that the cert rpms installed on the system are corresponding to those present in ~/ssl-build (or in the capsule certs tar.gz)

Added by Ivan Necas almost 8 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Installer
Target version:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1218251
Description of problem:

The katello-installer and capsule-certs-generate are using rpms to distribute the generated certificates. Newly-regenerated rpms with new certificates have increased version number, so that they should updated the previous certificates in the system.

However, in some cases (especially when experimenting with different katello-installer certs options and trying to re-install the katello), the rpms with the newly generated certificates installed on the system don't update already installed rpms on the system from previous attempts.

How reproducible:
always

Steps to Reproduce:
1. katello-installer
2. remove ~/ssl-build directory on the server
3. katello-installer --reset
4. capsule-certs-generate capsule-certs-generate --capsule-fqdn capsule.example.com --certs-tar ~/capsule.example.com.tar.gz
5. on the capsule: capsule-installer (using the options suggested in the capsule-certs-generate output)

Actual results:

The capsule-installer fails on

ProxyAPI::ProxyException: ERF12-2749 [ProxyAPI::ProxyException]: Unable to get environments from Puppet ([OpenSSL::SSL::SSLError]: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verif...) for proxy https://capsule.example.com:9090/puppet

Expected results:

The katello-installer, capsule-certs-generate and capsule-installer check that the cert rpms installed on the system correspond with the rpms that are intended to be used.

Additional info:

The workaround for the issue is to remote the cert rpms manually before the installer call:

for i in $(ls /etc/pki/katello-certs-tool/certs/*); 
do
rpm -e $(rpm -qf $i)
done

The run of the installer should make the installer work again.

There is a kcs article about this workaround https://access.redhat.com/solutions/1311844 with a small suggested update here https://bugzilla.redhat.com/show_bug.cgi?id=1171841#c18

Actions #1

Updated by Ivan Necas almost 8 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/puppet-certs/pull/91 added
Actions #2

Updated by Justin Sherrill almost 8 years ago

  • Status changed from Ready For Testing to Closed
  • translation missing: en.field_release set to 171
  • Difficulty set to medium
Actions #3

Updated by Eric Helms almost 8 years ago

  • Pull request https://github.com/Katello/puppet-certs/pull/92 added
Actions #4

Updated by Eric Helms over 7 years ago

  • translation missing: en.field_release changed from 171 to 162
Actions

Also available in: Atom PDF