ansible galaxy install missing file for v1.6.9
See original GitHub issueI am getting the following error from my playbook configuring a proxmox 7 cluster:
fatal: [xxx.xxx.com]: FAILED! => {"ansible_facts": {}, "ansible_included_var_files": [], "changed": false, "message": "Could not find or access 'debian-bullseye.yml'\
I believe this to be caused by the ansible-galaxy install the contains the incorrect files:
ansible-galaxy install lae.proxmox
Starting galaxy role install process
- downloading role 'proxmox', owned by lae
- downloading role from https://github.com/lae/ansible-role-proxmox/archive/v1.6.9.tar.gz
- extracting lae.proxmox to ~/.ansible/roles/lae.proxmox
- lae.proxmox (v1.6.9) was installed successfully
ls ~/.ansible/roles/lae.proxmox/vars/
debian-buster.yml debian-stretch.yml main.yml
debian-bullseye.yml is missing, but is present on github. Something is wrong with the download build artifact.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Installing content — Ansible Documentation
Install a specific version of a role by appending a comma and a version tag. For example, the following installs v1.0.0 of the...
Read more >ansible-galaxy install fails with no useful error message #65179
SUMMARY To use a recent git on RHEL7 I installed git from SoftwareTools /opt/rh/rh-git29/root/usr/bin/git ISSUE TYPE Bug Report COMPONENT ...
Read more >ansible-galaxy - specify version range to install - Stack Overflow
What am I missing? Edit: I'm using ansible / ansible-galaxy 2.9.16 but I expect a solution that will still works with ansible 2.10....
Read more >Release 1.0 - Ansible Galaxy FortiOS Collection
This document explains how to install the FortiOS Ansible Galaxy Collection. 2.1 Install Python3. • Follow steps in https://www.python.org/ ...
Read more >Galaxy Installation with Ansible
Galaxy is cloned (or updated); A virtualenv is created if it doesn't exist; Configuration files are installed; Any missing dependencies are installed ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
No. That looks like it would be an issue with your role variables (specifically
pve_group
) and/or inventory. Since that’s the default, I’m guessing you didn’t make aproxmox
group in your inventory? Please make sure to read through the README in any case (and if it is missing anything let me know).Anyway, the PR I’m talking about is https://github.com/lae/ansible-role-proxmox/pull/173 and it’s been tested out a bit already; a review to make sure nothing is missing in the proposed changes is what I would want. I’ll try to review it myself later since quite some time has already passed, though.
thank you - it is working.