-
Bug
-
Resolution: Done-Errata
-
Normal
-
6.15.0
-
Phoenix - Content
-
3
-
False
-
pulpcore-3.55.0, pulpcore-3.39.15, pulpcore-3.49.10
-
Moderate
-
Sprint 137, Sprint 138, Sprint 139, Sprint 140, Sprint 141
-
None
-
None
-
None
-
Automated
-
No
Description of problem:
How reproducible:
Is this issue a regression from an earlier version:
Steps to Reproduce:
1.
2.
3.
Actual behavior:
[Describe the issue in detail, including what is happening and where]
Expected behavior:
[Describe what should be happening instead]
Business Impact / Additional info:
- is cloned by
-
-
- Closed
-
- external trackers
- links to
-
RHBA-2024:140284
Important: Satellite 6.16.0 release
[SAT-25194] Export of large amount of packages will result in errors
This also affects the ability to reclaim space for the satellite as whole from Infrastructure -> Capsules
Can we have the fix backported to 6.15 atleast ?
Eric Helms
added a comment - This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues@redhat.com. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Eric Helms
added a comment - This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues@redhat.com. You can also visit https://access.redhat.com/articles/7032570 for general account information. Possible workaround for users exporting only RPM content is using syncable format, which is not affected by this issue
~~~
hammer content-export complete version --content-view="CV_NAME" --organization-id=1 --version=1.0 --format syncable
~~~
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Critical: Satellite 6.16.0 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-2024:8906