-
Notifications
You must be signed in to change notification settings - Fork 638
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
control_plane_ee_image cannot override the default #685
Comments
Something still writes the quay.io one on top of my own default control plane ee image at some point after a few redeploys, won't have time to debug it though as the user decided to just specify their own control plane all the time. It's quite problematic because the default image does not include the community.general collection which contains many modules that were built-in previous ansible releases ansible/awx-ee#65 which means that the default awx-ee image is not expected to work for most use cases (playbooks developed on previous ansible releases) |
Very much same issue here, I fixed it by attaching execution_environment.py.j2 from operator version 0.14.0 to an operator instance.
Definitely an issue with ordering, as you mentioned secret is created before custom control plane variable being processed. This might be a commit introducing problem. |
@marekzebro is it sticking for you after a bunch of re-applies on the AWX object? |
@jpic, it is staying there. As far I know configuration is being read from -app-credentials secret object. execution_environment.py.j2 injects key to this secret. Unfortunately I have additional problem with control plane execution environment not executing project updates on AWX 19.5.0, works completely fine with previous version. |
Hello, Same issue, some news ? Regards, |
If you are operating in a closed environment that does not have access to the internet, this issue makes it impossible to upgrade beyond 19.4.0. Until this problem is resolved any upgrade for us is impossible. 19.5.1 exhibits the behaviour talked about in this issue. If you are offline.... you don't have access to the default image locations on the internet, you have to override them. This override is broken after 19.4.0. |
Almost two years on. No solution? Any ideas where to look next? |
Didn't that work for you? #685 (comment) |
We got it figured out. Here are the details for others to follow without needing to fully dig into all the details though; YMMY depending on versions. Need to create a config map from the execution_environment.py.j2 file above.
Modify the AWX controller deployment to use the above config map
Volume section
The above changes worked for us based on the #685 (comment) comment above. |
does #1740 fix this? |
Probably but I'm on a version prior to the merge and need to control the
upgrade process.
…On Mon, Aug 5, 2024 at 12:38 PM Luke Bodeen ***@***.***> wrote:
does #1740 <#1740> fix this?
—
Reply to this email directly, view it on GitHub
<#685 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABSNO2DPQ3K3SYKW5NOK6DZP7IE5AVCNFSM5JRTCYFKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMRWHE3TOOBXGA2Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
ISSUE TYPE
SUMMARY
_custom_control_plane_ee_image is set after executions_environments.py is rendered.
ENVIRONMENT
STEPS TO REPRODUCE
Set control_plane_ee_image to a non-default value.
EXPECTED RESULTS
That AWX "Control Plane Execution Environment" uses control_plane_ee_image.
ACTUAL RESULTS
"Control Plane Execution Environment" has quay.io/ansible/awx-ee:latest anyway.
ADDITIONAL INFORMATION
This is because AWX uses the value from executions_environments.py.js, which is rendered by app_credentials.yaml.js, which wants to use
_custom_control_plane_ee_image
as intended.But,
_custom_control_plane_ee_image
is set after the templates in question are rendered:_custom_control_plane_ee_image
happens in resources_configuration.yml line 20_custom_control_plane_ee_image
is set in resources_configuration.yml line 83WORK AROUND
One will try setting
CONTROL_PLANE_EXECUTION_ENVIRONMENT
incustom.py
, and indeed,/etc/tower/conf.d/custom.py
will haveCONTROL_PLANE_EXECUTION_ENVIRONMENT=your/value
.But,
/etc/tower/conf.d/execution_environments.py
will still containCONTROL_PLANE_EXECUTION_ENVIRONMENT=quay.io/ansible/awx-ee:latest
.The latter will shadow the former because Tower conf.d/*.py are read one by one by glod in tower settings.
Solution
CONTROL_PLANE_EXECUTION_ENVIRONMENT=your/value
to your custom.py, and alsomountPath: /etc/tower/conf.d/custom.py
withmountPath: /etc/tower/conf.d/z_custom.py
,Or use
extra_settings
because it should hardcode them at the end of production settings but I've not tested that one.Don't forget to also set control_plane_ee_image just in case ;)
The text was updated successfully, but these errors were encountered: