The default execution environment cannot even run an ansible job with built-in modules. Had to use alternative images to build a custom execution environment to successfully run a job

[muralihcl]

The default execution environment cannot even run an ansible job with built-in modules (
ghcr.io/ctrliq/ascender-ee:latest). Had to use alternative image to build a custom execution environment to successfully run a job.

Attempt to run a Job template with the default execution environment gave error for ansible.builtin.ufw and community.general.ufw modules. The base image does not even have Python3, so customizing packages always results in a failed build. I could not explore the ghcr.io registry, so not sure if any other variants could be of use here.

When tried with a CentOS9 based custom execution environment, which I have built with ansible core 2.15.x and ansible version 8.7 with all necessary collections and pip packages, I never faced any challenges while running the ansible job.

What is missing here?

[michaelford85]

@muralihcl Are you certain that there is a ansible.builtin.ufw module? I'm not seeing that there is one in the documentation. Regarding the community.general collection, I'll see if that's part of the execution environment.

[muralihcl]

Apparently, ansible.builtin.ufw gets redirected to community.general.ufw. But, I still cannot run the jobs with the default execution environment.

The execution environment is pointing to the image ghcr.io/ctrliq/ascender-ee:latest and it is set to never pull the image.

The containerd shows the image is present on the system via 'crictl image ls'.

I customized an execution environment and tagged it to be visible as custom-ee and setup the execution environment pull policy to never.

With Ascender-EE(latest), I still cannot run the job. It says, unable to resolve community.general.ufw module. With Custom execution environment, I can run the job without any challenge.