This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2262379 - Library import of an Ansible Collection repo fails
Summary: Library import of an Ansible Collection repo fails
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.15.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Gerrod
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-02 10:40 UTC by Vladimír Sedmík
Modified: 2024-06-17 01:12 UTC (History)
10 users (show)

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:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:01:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github pulp pulp_ansible issues 1764 0 None closed Import fails due to AnsibleNamespaceMetadata not being exported. 2024-03-01 14:21:15 UTC
Red Hat Issue Tracker   SAT-23051 0 None Migrated None 2024-06-17 01:12:15 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.