Project

Profile

Help

Issue #9520

pulp_installer collection can't be built by Ansible 2.9, breaking pulplift

Added by evgeni about 1 month ago. Updated about 1 month ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 107
Quarter:

Description

Ohai,

when trying to use pulplift with Ansible 2.9 (on Fedora 34), I get an error that the collection can't be installed:

% vagrant up pulp3-sandbox-centos7
…
TASK [Building pulp.pulp_installer] ********************************************
changed: [pulp3-sandbox-centos7 -> localhost]
 
TASK [Installing pulp.pulp_installer] ******************************************
failed: [pulp3-sandbox-centos7 -> localhost] (item=/home/evgeni/Devel/pulp/pulp_installer/vagrant/playbooks/../../pulp-pulp_installer-3.16.0.tar.gz) => {"ansible_loop_var": "item", "changed": true, "cmd": ["ansible-galaxy", "collection", "install", "--force", "/home/evgeni/Devel/pulp/pulp_installer/vagrant/playbooks/../../pulp-pulp_installer-3.16.0.tar.gz"], "delta": "0:00:06.411039", "end": "2021-10-19 09:59:56.416068", "item": "/home/evgeni/Devel/pulp/pulp_installer/vagrant/playbooks/../../pulp-pulp_installer-3.16.0.tar.gz", "msg": "non-zero return code", "rc": 250, "start": "2021-10-19 09:59:50.005029", "stderr": "\u001b[0;31mERROR! Unexpected Exception, this is probably a bug: \"linkname 'molecule/release-static/../scenario_resources/debian-redis-server.service' not found\"\u001b[0m", "stderr_lines": ["\u001b[0;31mERROR! Unexpected Exception, this is probably a bug: \"linkname 'molecule/release-static/../scenario_resources/debian-redis-server.service' not found\"\u001b[0m"], "stdout": "Process install dependency map\n|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\bStarting collection install process\n|\bInstalling 'pulp.pulp_installer:3.16.0' to '/home/evgeni/.ansible/collections/ansible_collections/pulp/pulp_installer'\n/\b-\b\\\bto see the full traceback, use -vvv", "stdout_lines": ["Process install dependency map", "|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\b-\b\\\b|\b/\bStarting collection install process", "|\bInstalling 'pulp.pulp_installer:3.16.0' to '/home/evgeni/.ansible/collections/ansible_collections/pulp/pulp_installer'", "/\b-\b\\\bto see the full traceback, use -vvv"]}
 
PLAY RECAP *********************************************************************
pulp3-sandbox-centos7      : ok=5    changed=2    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0   

This is because when building the pulp_installer collection with Ansible 2.9, the "molecule" folder ends up in the built collection tarball (as 2.9 doesn't understand build_ignore in galaxy.yml).

I think it would be nice if the collection/pulplift could be really used with Ansible 2.9, as documented ;-)

Associated revisions

Revision 3579b9f5 View on GitHub
Added by Fabricio Aguiar about 1 month ago

Fix pulplift for installations with ansible 2.9

closes #9520

Revision 3579b9f5 View on GitHub
Added by Fabricio Aguiar about 1 month ago

Fix pulplift for installations with ansible 2.9

closes #9520

History

#1 Updated by fao89 about 1 month ago

  • Category set to Installer - Moved to GitHub issues
  • Status changed from NEW to ASSIGNED
  • Assignee set to fao89
  • Triaged changed from No to Yes
  • Sprint set to Sprint 107

#2 Updated by pulpbot about 1 month ago

  • Status changed from ASSIGNED to POST

#3 Updated by Anonymous about 1 month ago

  • Status changed from POST to MODIFIED

Please register to edit this issue

Also available in: Atom PDF