starred/proxmoxer

Fork 0

mirror of https://github.com/proxmoxer/proxmoxer.git synced 2026-04-25 07:06:00 +03:00

[GH-ISSUE #37] "proxmoxer required for this module", yet proxmoxer is installed on Macos #18

New issue

Closed

opened 2026-02-27 15:45:59 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 15:45:59 +03:00

Owner

Originally created by @bronsgeest on GitHub (Oct 4, 2020).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/37

When executing an ansible playbook on Macos Catalina (Apple) I continue to have the fatal error: "fatal: [proxy-test]: FAILED! => {"changed": false, "msg": "proxmoxer required for this module"}

This is not a proxmoxer issue, but some Apple thing I assume.

pip3 show proxmoxer 1.1.1, Location: /usr/local/lib/python3.8/site-packages
ansible 2.9.13 using python version = 3.8.5
Macos: 10.15.7

Initially poxmoxer was installed in python3.7/site-packages. Removing and reinstalling proxmoxer wiht pip3 fixed that and it is now in python3.8/site-packages. Yet the behaviour remains the same. I can run the same playbook normally when I "ssh -A" into a debian10 VM running on the same Apple laptop.

What extra debug info can I enable to find the reason for the error? Is someone familiar with the same behaviour on an Apple and was that fixed?

Max

Originally created by @bronsgeest on GitHub (Oct 4, 2020). Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/37 When executing an ansible playbook on Macos Catalina (Apple) I continue to have the fatal error: "fatal: [proxy-test]: FAILED! => {"changed": false, "msg": "proxmoxer required for this module"} This is not a proxmoxer issue, but some Apple thing I assume. pip3 show proxmoxer 1.1.1, Location: /usr/local/lib/python3.8/site-packages ansible 2.9.13 using python version = 3.8.5 Macos: 10.15.7 Initially poxmoxer was installed in python3.7/site-packages. Removing and reinstalling proxmoxer wiht pip3 fixed that and it is now in python3.8/site-packages. Yet the behaviour remains the same. I can run the same playbook normally when I "ssh -A" into a debian10 VM running on the same Apple laptop. What extra debug info can I enable to find the reason for the error? Is someone familiar with the same behaviour on an Apple and was that fixed? Max

kerem

2026-02-27 15:45:59 +03:00

closed this issue
added the
status:ansible-issue
label

kerem commented

2026-02-27 15:46:00 +03:00

Author

Owner

@jhollowe commented on GitHub (Oct 5, 2020):

This seems to be an issue with Ansible, not proxmoxer. Please file a bug report with Ansible so people with knowledge of Ansible can help you with this issue.

@jhollowe commented on GitHub (Oct 5, 2020): This seems to be an issue with Ansible, not proxmoxer. Please file a [bug report with Ansible](https://github.com/ansible/ansible/issues/new?template=bug_report.md) so people with knowledge of Ansible can help you with this issue.

kerem commented

2026-02-27 15:46:00 +03:00

Author

Owner

@bronsgeest commented on GitHub (Oct 7, 2020):

Thx for your reply, I did not expect ansible could be the problem. I will follow up with them.

@bronsgeest commented on GitHub (Oct 7, 2020): Thx for your reply, I did not expect ansible could be the problem. I will follow up with them.

kerem referenced this issue

2026-02-27 15:46:38 +03:00

[PR #22] [MERGED] handle empty stderr from ssh connections #137

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/proxmoxer#18

No description provided.

Rows
Columns