Chapter 5. Known issues
This section describes known issues in Red Hat Satellite 6.16.
5.1. Web UI
Unable to specify a custom organization label in the Satellite web UI
When creating a new organization in the Satellite web UI, the field to specify a custom label for the organization is missing. Each time you create a new organization from the Satellite web UI, Satellite creates a default label which mirrors the organization name. For example, if you create an organization named New Organization, Satellite creates a label named New_Organization. Note that you cannot change the label after it is created.
To work around this problem, create new organizations from CLI by using the hammer organization create command and pass the --label option to specify a custom label. For more information, see Creating an Organization in Administering Satellite.
5.2. Security and authentication
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
For more details, see a related Knowledgebase solution. Note that the problem has been fixed for hosts that run RHEL 9.4 or later. See also Chapter 6, Bug fixes.
Jira:SAT-28297[1]
5.3. Content management
Repositories listed but not active
The Red Hat Repositories page lists the Red Hat Satellite 6 Client 2 repositories as recommended repositories, but these repositories are not active yet. Continue using Red Hat Satellite Client 6 repositories.
Organization deletion fails
If there are container push repositories among the organization’s products, then organization deletion fails. To work around this problem, delete the container push repositories before deleting the organization.
Concurrently synchronizing many large repositories to a Capsule might cause core dumps for the pulpcore-api
The pulpcore-api might experience core dumps when multiple large repositories are synchronized to a Capsule concurrently. When this problem occurs, the following error message is displayed in /var/log/messages: capsule systemd-coredump[16056]: Process 9867 (pulpcore-api) of user 988 dumped core. The synchronization completes successfully despite the errors.
5.4. Users and roles
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]
