-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
community.general.proxmox inventory plugin fails for a cluster setup in 9.3.0 #8798
Closed
1 task done
Comments
Files identified in the description:
If these files are incorrect, please update the |
ansibullbot
added
bug
This issue/PR relates to a bug
module
module
plugins
plugin (any type)
traceback
labels
Aug 25, 2024
!component =plugins/inventory/proxmox.py |
Files identified in the description: If these files are incorrect, please update the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
When I tried to run a community.general.proxmox inventory plugin with 9.3.0, it fails with an exception. Rolling back to 9.2.0 works
Issue Type
Bug Report
Component Name
plugins/inventory/proxmox.py
Ansible Version
Community.general Version
Configuration
OS / Environment
Bazzite (Fedora based) with ansible installed using conda
Steps to Reproduce
Run the following command
$ ansible-inventory -i inventory --graph -vvvv
Expected Results
Graph of inventory returned with no errors/exceptions
Actual Results
I have tried some prelim debugging by adding print calls in the
_get_json
function:Running over many times, I found that
json['data']
is notNone
when the lxc container is running onpve2
(but not the other nodepve1
in the same cluster.pve.pitwinken.com
is a reverse proxy with load balancing pointing to one of the nodes. Currently it is reverse proxying frompve2
.Further investigation leads to the discovery of bug in Proxmox API that the return data is none if the lxc container is running on other nodes of the same cluster. I have opened a bug report on Proxmox's bug tracker. But it'd be great if the plugin can handle
json['data']
beingNone
gracefully anyway.Code of Conduct
The text was updated successfully, but these errors were encountered: