This repository has been archived by the owner on Jan 5, 2023. It is now read-only.
fix: make sure directory for async is correctly set #178
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In certain cases where the home directory environment variable (
$HOME) is set and it doesn't match the home directory in/etc/passwdtheasync_statustask will fail with a message such as:This fixes that issue by setting the
HOMEenvironment variable as theansible_async_dirvariable that 'async_status' task accepts as a override.I ran into this issue with the
creator-eecontainer that is supposedly going to be fixed but I'm proposing this change as this issue could still occur in other containers/environments.Related:
ansible/ansible-runner#1024
ansible/creator-ee#19
ansible/ansible-runner#1027
#139
ansible-community/molecule-podman#139