I’m confused about the Job Isolation functionality in AWX. The documentation indicates that it should be on by default (https://github.com/ansible/awx/blob/devel/docs/process_isolation.md), but in practice it seems to be permanently disabled (https://github.com/ansible/awx/blob/devel/installer/image_build/files/settings.py#L29) - in the web UI it is off and can’t be enabled due to AWX coming with config that disables it.
I’d gotten used to jobs being isolated from each other on Tower, and am now hitting problems where concurrent jobs may occasionally have both written a localhost temp file at the same time and the same place on localhost, and then get into trouble. Basically, I got used to the idea that any given job could treat the localhost filesystem as being ‘its own’.
Is Job Isolation just not possible on AWX, or is that something coming in a future update?
Thanks,
Robin
Robin Miller (robincello@gmail.com) said:
I'm confused about the Job Isolation functionality in AWX. The
documentation indicates that it should be on by default
(https://github.com/ansible/awx/blob/devel/docs/process_isolation.md), but
in practice it seems to be permanently disabled
(https://github.com/ansible/awx/blob/devel/installer/image_build/files/settings.py#L29)
- in the web UI it is off and can't be enabled due to AWX coming with
config that disables it.
I'd gotten used to jobs being isolated from each other on Tower, and am now
hitting problems where concurrent jobs may occasionally have both written a
localhost temp file at the same time and the same place on localhost, and
then get into trouble. Basically, I got used to the idea that any given job
could treat the localhost filesystem as being 'its own'.
Is Job Isolation just not possible on AWX, or is that something coming in a
future update?
My understanding is that it was an initial limitation of the container env,
and it will be fixed at some point.
Bill