-
Notifications
You must be signed in to change notification settings - Fork 63
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
Can not run ansible playbooks from F39 #3018
Closed
Tracked by
#2964
praiskup opened this issue
Nov 22, 2023
· 0 comments
· Fixed by praiskup/resalloc-aws#12 or fedora-copr/resalloc-ibm-cloud#23
Closed
Tracked by
#2964
Can not run ansible playbooks from F39 #3018
praiskup opened this issue
Nov 22, 2023
· 0 comments
· Fixed by praiskup/resalloc-aws#12 or fedora-copr/resalloc-ibm-cloud#23
Labels
Comments
praiskup
added a commit
to praiskup/resalloc-aws
that referenced
this issue
Nov 22, 2023
This is the way around weird F39+ bug causing ansible-playbook failure: ERROR: Ansible requires blocking IO on stdin/stdout/stderr. Non-blocking file handles detected: <stdin> Fixes: fedora-copr/copr#3018
praiskup
added a commit
to praiskup/resalloc-aws
that referenced
this issue
Nov 22, 2023
This is the way around weird F39+ bug causing ansible-playbook failure: ERROR: Ansible requires blocking IO on stdin/stdout/stderr. Non-blocking file handles detected: <stdin> Fixes: fedora-copr/copr#3018
praiskup
added a commit
to praiskup/resalloc-ibm-cloud
that referenced
this issue
Nov 28, 2023
praiskup
added a commit
to fedora-copr/resalloc-ibm-cloud
that referenced
this issue
Jan 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: