Project

General

Profile

Actions

Bug #21740

closed

Reenable sync step fails when hammer is not properly configured

Added by Lukas Zapletal over 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
High
Category:
Upgrades
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Reenable sync does fail for a HTB CU with:

                               re-enable sync plans:
                \ re-enabling sync plans                                              [FAIL]
                Could not load the API description from the server: SSL certificate verification failed
                Make sure you configured the correct URL and have the server's CA certificate installed on your system.

                The following configuration option were used for the SSL connection:
                  ssl_ca_file = /etc/pki/katello/certs/katello-default-ca.crt

                Make sure the location contains an unexpired and valid CA certificate for https://xxxxxxxx.com

                Could not load the API description from the server: SSL certificate verification failed
                Make sure you configured the correct URL and have the server's CA certificate installed on your system.

                The following configuration option were used for the SSL connection:
                  ssl_ca_file = /etc/pki/katello/certs/katello-default-ca.crt

Perhaps add additional check that will verify if certs are correct prior doing any hammer command.

It is worth nothing that hammer command was not working for this customer because of https://bugzilla.redhat.com/show_bug.cgi?id=1513599 but these symptoms are different (cert vs password).


Related issues 1 (0 open1 closed)

Related to Foreman Maintain - Feature #22739: formain-maintain fails to use hammer if config has host: localhostClosedMartin Bacovsky03/01/2018Actions
Actions

Also available in: Atom PDF