Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJoniel Pasqualetto
2022-01-20 21:52:27 UTC
Description of problem:
If a previous import attempt left an importer created on pulp and a new import task is created with the same source tarball, the new task fails complaining about the importer already being created.
There's no easy way to cleanup the importer (from a user perspective).
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Start an import task
2. make the import task fail unexpectedly (kill the worker importing it, for example)
3. cancel/cleanup the task (if you skip the failed step and resume, the importer will be removed)
4. Cleanup the imported CV on Satellite
5. Try importing again
Actual results:
~~~
# hammer content-import version --organization-id 5 --path /var/lib/pulp/imports/test3_kickstart_rhel7/1.0/2022-01-14T11-34-09-05-00/
[............................. ] [13%]
Error: Error message: the server returns an error
HTTP status code: 400
Response headers: {"Date"=>"Thu, 20 Jan 2022 21:48:48 GMT", "Server"=>"gunicorn", "Content-Type"=>"application/json", "Vary"=>"Accept,Cookie", "Allow"=>"GET, POST, HEAD, OPTIONS", "X-Frame-Options"=>"SAMEORIGIN", "Content-Length"=>"39", "Correlation-ID"=>"28a90f8e-405b-444c-ba13-c80d62b06632", "Access-Control-Expose-Headers"=>"Correlation-ID", "Via"=>"1.1 bombsat610.usersys.redhat.com", "Connection"=>"close"}
Response body: {"name":["This field must be unique."]}
~~~
Expected results:
Import should work anyway or at least return a more meaningful error.
Additional info:
I prepared complete and incremental exports of few Content Views and Libraries. Then I tried to import them and killed the import task (kill pulpcore-worker). Importers were cleaned up automatically. Re-import of CVs and Libraries was successful.
VERIFIED with Satellite 6.11 SNAP 17.0 @ RHEL8.5
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.11 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-2022:5498
Description of problem: If a previous import attempt left an importer created on pulp and a new import task is created with the same source tarball, the new task fails complaining about the importer already being created. There's no easy way to cleanup the importer (from a user perspective). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start an import task 2. make the import task fail unexpectedly (kill the worker importing it, for example) 3. cancel/cleanup the task (if you skip the failed step and resume, the importer will be removed) 4. Cleanup the imported CV on Satellite 5. Try importing again Actual results: ~~~ # hammer content-import version --organization-id 5 --path /var/lib/pulp/imports/test3_kickstart_rhel7/1.0/2022-01-14T11-34-09-05-00/ [............................. ] [13%] Error: Error message: the server returns an error HTTP status code: 400 Response headers: {"Date"=>"Thu, 20 Jan 2022 21:48:48 GMT", "Server"=>"gunicorn", "Content-Type"=>"application/json", "Vary"=>"Accept,Cookie", "Allow"=>"GET, POST, HEAD, OPTIONS", "X-Frame-Options"=>"SAMEORIGIN", "Content-Length"=>"39", "Correlation-ID"=>"28a90f8e-405b-444c-ba13-c80d62b06632", "Access-Control-Expose-Headers"=>"Correlation-ID", "Via"=>"1.1 bombsat610.usersys.redhat.com", "Connection"=>"close"} Response body: {"name":["This field must be unique."]} ~~~ Expected results: Import should work anyway or at least return a more meaningful error. Additional info: