Este contenido no está disponible en el idioma seleccionado.

Chapter 5. Known issues


This section describes known issues in Red Hat Satellite 6.16.

5.1. Installation and upgrade

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.

Jira:SAT-27979

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.

Jira:SAT-28297

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.

Jira:SAT-29303

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.

Jira:SAT-28387

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:

  1. Create your filter.
  2. Start editing the filter.
  3. 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]

Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2026 Red Hat
Volver arriba