-
Notifications
You must be signed in to change notification settings - Fork 359
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
ansible_runner cleaning up missing file... Device busy error continuously. #374
Comments
Best thing to do here is probably check for the non-existence and not fail outright if the directory is actually gone. |
How about something simple like this?
|
I'd love to see a root-cause here. We don't see this in the official AWX or Tower builds that include Runner. |
isn't this the same? |
Possibly, does that mean your RPM is using an old version of Runner? |
@matburt i see the rpm has a dependency on |
@matburt No, I'm using the version defined in awx.. But maybe this is related: ansible/awx#4073 never seems to be fixed?? |
Does #380 do anything for this for you? |
@wenottingham the |
This fixes it for me as well. I grabbed raw versions of the runner_config.py and runner.py and updated them in the codebase, then started AWX and running multiple jobs. All succeed/fail as required. |
Closing as fixed, then. Will be in 1.4.4. |
fixing issues related to: ansible/ansible-runner#374
I run the AWX-RPM version and when we upgraded to the newest code, which includes this newest release of ansible_runner/runner.py, we are continuing to see workflows that DID run without issue, to fail at the first playbook run (inventory syncs work, scm syncs work), but something about the playbook runs fail straight out.
The code starts at 253, which is the new section for cleaning up temp directories. I've tweaked time-outs, retries, everything except code rolling...
All failed.
Most of the time, I have seen that directory as being missing at the error point, so not sure if it is deleting or can't figure out that it needs to delete it AFTER it has gotten back out of it (as AWX runs inside the /tmp/* folder while running) and as such gives itself the Device busy error.
I rolled my code back to https://github.com/ansible/ansible-runner/blob/68d09d87b7941a4c5cd6efd03b344b1a916afa9a/ansible_runner/runner.py which is the commit prior to the clean-up code add, which is allowing us to work again.
Any thoughts/input on something else I could have been missing with the newest code?
The text was updated successfully, but these errors were encountered: