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 2270513 - Once LEAPP is not an option for FIPS server, backup and restore is one, but it's failing for smart-proxy
Summary: Once LEAPP is not an option for FIPS server, backup and restore is one, but i...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Proxy
Version: 6.14.3
Hardware: All
OS: All
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-03-20 17:03 UTC by Waldirio M Pinheiro
Modified: 2024-04-02 13:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-24073 0 None None None 2024-03-21 00:27:48 UTC

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:
Note You need to log in before you can comment on or make changes to this bug.