Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 5. Known issues
This section describes known issues in Red Hat Satellite 6.17.
5.1. Security and authentication Copier lienLien copié sur presse-papiers!
Unable to upload an OpenSCAP report from hosts that run RHEL 9.3 or earlier with FIPS mode enabled
On Satellite hosts that run RHEL 9.3 or earlier with FIPS mode enabled, uploading an OpenSCAP report fails with the following error:
Unable to load certs Neither PUB key nor PRIV key
Unable to load certs
Neither PUB key nor PRIV key
For more details, see a related Knowledgebase solution. Note that the problem has been fixed for hosts that run RHEL 9.4 or later.
5.2. Host provisioning and management Copier lienLien copié sur presse-papiers!
OpenShift Virtualization cannot be added as a compute resource
You cannot add OpenShift Virtualization as a compute resource because the OpenShift Virtualization API has changed and is incompatible with Satellite 6.16 and later.
5.3. Users and roles Copier lienLien copié sur presse-papiers!
Newly created filters do not inherit organizations and locations associated with the role
When an organization and location are defined for a role, these organizations and locations are not propagated to the filters created within the role. Consequently, users with a role assigned can access resources in any other organization or location that they have sufficient permissions to view instead of only organizations and locations defined for the role.
To work around the problem:
- Create your filter.
- Start editing the filter.
- Save the filter without making any changes. This ensures that organizations and locations defined on the role level are propagated to filters correctly.
This known issue does not affect cloned roles. If you clone an existing role and assign organizations and locations to the cloned role, the organizations and locations are propagated to filters correctly.
Note that defining organizations and locations on the filter level is deprecated. See Overriding organizations and locations on the filter level.
Jira:SAT-28731[1]
5.4. IPv6 Copier lienLien copié sur presse-papiers!
virt-who is not supported on IPv6 networks in Satellite
Satellite does not support virt-who in an IPv6 network.
Additional configuration is required in IPv6-only networks when using kinit
for IdM and AD users
When Identity Management (IdM) or Active Directory (AD) are configured as external authentication sources for a Satellite Server that has only IPv6 connectivity, Kerberos authentication for external users fails. This known issue is caused by a bug in the System Security Services Daemon (SSSD) and occurs when the DNS name of the IdM or AD server can be translated to both an IPv4 and IPv6 address but the IPv4 address is not accessible, for example because it is blocked by a firewall.
To work around this problem, configure the lookup_family_order
option in the [domain/<domain_name>]
in the /etc/sssd/sssd.conf
file:
[domain/_<example.com>_] lookup_family_order = ipv6_only
[domain/_<example.com>_]
lookup_family_order = ipv6_only
Jira:SAT-32530, Jira:SSSD-2511
IPv6 address entry in Satellite does not match the IPv6 address of a provisioned host
When you provision a host in an IPv6 network, Satellite contains an IPv6 address that does not match the actual IPv6 address of the host. This mismatch impairs host management capabilities, such as remote execution.
As a workaround, you can execute subscription-manager facts --upload
on the host or wait for the next facts upload to resolve the issue.
Host Discovery fails in an IPv6 network
When you attempt to discover an unknown host in an IPv6 network, the discovery fails with Error: 1001: Failed to open TCP connection to satellite.example.com:443
.
Failure to provision hosts in PXE-less Discovery over IPv6
After PXE-less host discovery on an IPv6 Satellite, when the host starts provisioning, it fails to resolve Satellite. As a result, the host fails to fetch Kickstart and the required files.