Bug 2004397
| Summary: | Sync of a Kickstart repo to the N-1 capsule fails | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Vladimír Sedmík <vsedmik> |
| Component: | Pulp | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Vladimír Sedmík <vsedmik> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.10.0 | CC: | dalley, ggainey, jsherril, rchan, ttereshc, zhunting |
| Target Milestone: | 6.10.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
Cause:
Attempting to synchronize a Kickstart repository to a Satellite 6.9 Capsule (running Pulp 2) fails with an importer error.
Consequence:
Synchronization of kickstart repository to Satellite 6.9 Capsule fails.
Workaround (if any):
1. Set the Download Policy of the kickstart repository to 'Immediate'
2. Synchronize the repository at the Satellite
3. Synchronize the environment containing the repository to the Capsule. If the repository is in a non-Library environment, the content view that it is a member of must be published and promoted to that environment.
Result:
The synchronization of the Satellite 6.9 capsule will be successful.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-16 14:13:51 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
Vladimír Sedmík
2021-09-15 08:13:16 UTC
Justin, Based upon the description, should this be proposed for Satellite 6.9.z or 6.10? I am assuming 6.9.z as it appears the error is on the Capsule (running 6.9). Thanks! I'm not sure we know enough about whether this is a problem with the 6.10 Satellite server or the 6.9 capsule server. The error was thrown on the capsule server, but that may not be where the fix (if there is one) ends up. I think the pulp team needs to investigate to figure that out. I suspect this is the same issue as https://pulp.plan.io/issues/9213 Which was fixed by pulpcore 3.14.6, released Sept 2, but not in the latest snaps yet. The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug. The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug. Verified on 6.10.0 snap 21 with python3-pulpcore-3.14.7-1.el7pc.noarch - successfully synced rhel-7-server-kickstart, rhel-8-for-x86_64-baseos-kickstart and rhel-8-for-x86_64-appstream-kickstart to the 6.9.6 capsule Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:4702 |