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
When enabling the Embedded Ansible role on the UI nodes for a ManageIQ region we have deployed (on Najdorf), we expected Ansible playbooks running on those nodes to start working immediately. However, we instead saw Error: [Permission denied @ rb_sysopen - /var/www/miq/vmdb/data/git_repos/locks/9] when attempting to run a playbook defined in an Ansible repository.
Checking the git_repos/ and git_repos/locks/ directory, I can see that all repos + locks EXCEPT those for the Ansible repos are owned by manageiq - however, the Ansible repos (and associated locks) are owned by root. Updating the ownership here to manageiq appears to resolve the issue.
Not sure if this is something that's addressed in later versions but wanted to open this for awareness in case.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
When enabling the Embedded Ansible role on the UI nodes for a ManageIQ region we have deployed (on Najdorf), we expected Ansible playbooks running on those nodes to start working immediately. However, we instead saw
Error: [Permission denied @ rb_sysopen - /var/www/miq/vmdb/data/git_repos/locks/9]
when attempting to run a playbook defined in an Ansible repository.Checking the git_repos/ and git_repos/locks/ directory, I can see that all repos + locks EXCEPT those for the Ansible repos are owned by manageiq - however, the Ansible repos (and associated locks) are owned by root. Updating the ownership here to manageiq appears to resolve the issue.
Not sure if this is something that's addressed in later versions but wanted to open this for awareness in case.
The text was updated successfully, but these errors were encountered: