Bug 2270513

Summary:	Once LEAPP is not an option for FIPS server, backup and restore is one, but it's failing for smart-proxy
Product:	Red Hat Satellite	Reporter:	Waldirio M Pinheiro <wpinheir>
Component:	Foreman Proxy	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.14.3	CC:	aruzicka, ehelms, rlavi
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged, WorkAround
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 17:26:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Waldirio M Pinheiro 2024-03-20 17:03:50 UTC

Description of problem:
Once LEAPP is not an option for FIPS server, backup and restore is one, but it's failing for smart-proxy.

Let's picture this scenario, satellite 6.11@rhel7 FIPS, backup created, and restored in a server with satellite 6.11@rhel8 FIPS.

Everything seems to be ok. However, when accessing the capsules / Puppet CA page, we can see errors as below
---
Failure: ERF50-5345 [Foreman::WrappedException]: Unable to connect ([ProxyAPI::ProxyException]: ERF12-5356 [ProxyAPI::ProxyException]: Unable to get PuppetCA certificates ([RestClient::NotAcceptable]: 406 Not Acceptable) for Capsule https://satellite_fqdn_here:9090/puppet/ca)
---

// Current crypto-policy status
---
# update-crypto-policies --show
FIPS
---

// Changing to LEGACY
---
# update-crypto-policies --set LEGACY
Warning: Using 'update-crypto-policies --set' in FIPS mode will make the system
non-compliant with FIPS.
It can also break the ssh access to the system.
Use 'fips-mode-setup --disable' to disable the system FIPS mode.
Setting system policy to LEGACY
Note: System-wide crypto policies are applied on application start-up.
It is recommended to restart the system for the change of policies
to fully take place.
---

// Checking once again
---
# update-crypto-policies --show
LEGACY
---

// Restarting satellite suite
---
foreman-maintain service restart
---

After that, there is no more error accessing this page, nor in the foreman-proxy logs.

Version-Release number of selected component (if applicable):
6.14

How reproducible:
100%

Steps to Reproduce:
1. Install sat611@rhel7 + FIPS + PuppetCA
2. Create a backup
3. Restore the backup on sat611@rhel8 + FIPS

Actual results:
Puppet CA page failing when crypto-policy is set to FIPS

Expected results:
Puppet CA page working when crypto-policy is set to FIPS

Additional info:

Comment 3 Eric Helms 2024-06-06 17:26:34 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.