Bug #21740

Reenable sync step fails when hammer is not properly configured

Added by Lukas Zapletal 8 months ago. Updated 6 days ago.

Status:Closed
Priority:High
Assignee:Martin Bacovsky
Category:Upgrades
Target version:-
Difficulty: Team Backlog:
Triaged: Fixed in Releases:
Bugzilla link: Found in Releases:
Pull request:https://github.com/theforeman/foreman_maintain/pull/165

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

Related to Foreman Maintain - Feature #22739: formain-maintain fails to use hammer if config has host:... Closed 03/01/2018

Associated revisions

Revision 8b3e44a2
Added by Martin Bacovsky 3 months ago

Fixes #22739, #21740 - Maintain hammer configuration

History

#1 Updated by Lukas Zapletal 8 months ago

  • Priority changed from Normal to High

HTB, I need triage please.

Can you simply add a step that will do "hammer ping" and if this fails the error will make more sense? I think this would be nice usability addition before GA ugprades.

#2 Updated by Martin Bacovsky 5 months ago

  • Target version set to 251
  • Assignee set to Martin Bacovsky

#3 Updated by Martin Bacovsky 5 months ago

  • Status changed from New to Assigned

#4 Updated by Martin Bacovsky 5 months ago

  • Related to Feature #22739: formain-maintain fails to use hammer if config has host: localhost added

#5 Updated by The Foreman Bot 3 months ago

  • Pull request https://github.com/theforeman/foreman_maintain/pull/165 added

#6 Updated by Martin Bacovsky 3 months ago

  • % Done changed from 0 to 100
  • Status changed from Assigned to Closed

Also available in: Atom PDF