Bug 2262379

Summary: Library import of an Ansible Collection repo fails
Product: Red Hat Satellite Reporter: Vladimír Sedmík <vsedmik>
Component: PulpAssignee: Gerrod <gubben>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.15.0CC: ahumbe, dalley, dkliban, ggainey, gubben, iballou, mdellweg, paji, rchan, rlavi
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Regression, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: pulp-ansible-0.20.4, pulp-ansible-0.21.3, pulp-ansible-0.22.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 17:01:29 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 2024-02-02 10:40:30 UTC
Description of problem:
Library import when there is just one Ansible Collection repo (with two collections) in the export fails.

Although the first failure appeared in snap 8.0, now the test run fails against older snaps (where it previously passed) too, which feels like the culprit might be some change in the content itself. However, against 6.14.2 the test case succeeds even now, with the supposed content change.


Version-Release number of selected component (if applicable):
6.15.0


How reproducible:
always


Steps to Reproduce:
1. Run robottelo test id 71dd1e1a-caad-48be-a180-206c8aa78639
- or -
1. Create custom product and custom repo with ansible collection. Use
   theforeman.foreman, version: "2.1.0"
   theforeman.operations, version: "0.1.0"
2. Sync the repo.
3. Export library and import into another satellite.


Actual results:
The import fails with error
 {"traceback"=>"  File \"/usr/lib/python3.11/site-packages/pulpcore/tasking/tasks.py\", line 61, in _execute_task\n    result = func(*args, **kwargs)\n             ^^^^^^^^^^^^^^^^^^^^^\n  File \"/usr/lib/python3.11/site-packages/pulpcore/app/tasks/importer.py\", line 396, in import_repository_version\n    for a_batch in _import_file(ca_path, ContentArtifactResource, retry=True):\n  File \"/usr/lib/python3.11/site-packages/pulpcore/app/tasks/importer.py\", line 268, in _import_file\n    a_result = resource.import_data(data, raise_errors=True)\n               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n  File \"/usr/lib/python3.11/site-packages/import_export/resources.py\", line 813, in import_data\n    result = self.import_data_inner(\n             ^^^^^^^^^^^^^^^^^^^^^^^\n  File \"/usr/lib/python3.11/site-packages/import_export/resources.py\", line 882, in import_data_inner\n    raise row_result.errors[-1].error\n  File \"/usr/lib/python3.11/site-packages/import_export/resources.py\", line 712, in import_row\n    self.before_import_row(row, **kwargs)\n  File \"/usr/lib/python3.11/site-packages/pulpcore/app/modelresource.py\", line 115, in before_import_row\n    row[\"content\"] = self.linked_content[row[\"content\"]]\n                     ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^\n", "description"=>"'018d40b6-3df6-713c-ab1e-0a505a5e2f88'"}


Expected results:
It should succeed.

Comment 6 Partha Aji 2024-02-20 21:17:23 UTC
Updating component to pulp

Comment 10 Ian Ballou 2024-04-10 15:39:08 UTC
Matthias, Gerrod, does the closing of https://github.com/pulp/pulp_ansible/issues/1764 mean the issue is fully resolved?

Comment 12 Matthias Dellweg 2024-04-11 08:36:49 UTC
Yes, this patch fixes the issue we identified.
And it looks like we have packports in pulp_ansible 0.20.4 and 0.21.3 .

Comment 13 Eric Helms 2024-06-06 17:01:29 UTC
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. You can also visit https://access.redhat.com/articles/7032570 for general account information.