You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version
Server version: 4.6.4
Pulp Ansible Version: 0.15.0
Describe the bug
If there are collections published without meta/runtime.yml in the Automation Hub, the upgrade from Automation Hub 4.2 (AAP 1.2) to Automation Hub 4.6 (AAP 2.3) fails with the following error:
TASK [pulp.pulp_installer.pulp_database_config : Run database migrations] ******
fatal: [aap01dhub1new.launcher.int.abnamro.com]: FAILED! => {"changed": true, "cmd": ["/usr/bin/pulpcore-manager", "migrate", "--no-input"],
......
......
File \"/usr/lib/python3.9/site-packages/pulp_ansible/app/migrations/0030_collectionversion_requires_ansible.py\", line 33, in set_requires_ansible_and_manifest_and_files_json", " collection_version.requires_ansible = runtime_yaml.get(\"requires_ansible\")", "AttributeError: 'NoneType' object has no attribute 'get'"],
Version
Server version: 4.6.4
Pulp Ansible Version: 0.15.0
Describe the bug
If there are collections published without meta/runtime.yml in the Automation Hub, the upgrade from Automation Hub 4.2 (AAP 1.2) to Automation Hub 4.6 (AAP 2.3) fails with the following error:
To Reproduce
Expected behavior
The installer should show a Warning and skip that task if there is a collection without runtime.yml
Additional context
After applying the patch provided by Matthias Dellweg, the upgrade finishes successfully.
The text was updated successfully, but these errors were encountered: