Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2157627

Summary:	health check uses the wrong certificate bundle to talk to Foreman
Product:	Red Hat Satellite	Reporter:	Evgeni Golov <egolov>
Component:	Satellite Maintain	Assignee:	Evgeni Golov <egolov>
Status:	CLOSED ERRATA	QA Contact:	Eric Helms <ehelms>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.13.0	CC:	ehelms, jpathan, pcreech, rmynar
Target Milestone:	6.13.0	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-foreman_maintain-1.2.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-03 13:24:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Evgeni Golov 2023-01-02 12:24:02 UTC

Since https://github.com/theforeman/foreman_maintain/commit/b0337ee3 we pass the wrong certificate bundle to Net::HTTP, resulting in failing health checks

Reported in https://community.theforeman.org/t/foreman-maintain-health-check-fails/31716

Comment 1 Evgeni Golov 2023-01-02 12:24:06 UTC

Created from redmine issue https://projects.theforeman.org/issues/35892

Comment 2 Evgeni Golov 2023-01-02 12:24:07 UTC

Upstream bug assigned to egolov

Comment 3 Bryan Kearney 2023-01-02 16:03:30 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35892 has been resolved.

Comment 4 Evgeni Golov 2023-01-05 09:37:12 UTC

verification note: this needs to be verified with custom certificates, as otherwise the two certs are identical and the bug doesn't show up

Comment 5 Eric Helms 2023-02-03 19:17:54 UTC

I installed a 6.13 snap, added custom certificates and then tested health check:

# satellite-maintain health check
Running ForemanMaintain::Scenario::FilteredScenario
================================================================================
Check number of fact names in database:                               [OK]
--------------------------------------------------------------------------------
Check whether all services are running:                               [OK]
--------------------------------------------------------------------------------
Check whether all services are running using the ping call:           [OK]
--------------------------------------------------------------------------------
Check for paused tasks:                                               [OK]
--------------------------------------------------------------------------------
Check whether system is self-registered or not:                       [OK]
--------------------------------------------------------------------------------

Comment 8 errata-xmlrpc 2023-05-03 13:24:04 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 (Important: Satellite 6.13 Release), 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-2023:2097