-
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
AWX fails to start on IPv6 disabled environments #1017
Comments
Probably broke in #950 If someone can open a PR adding variables to enable / disable ipv4/ipv6 we can get that reviewed and tested. |
@shanemcd I gave it a try. Could you have a quick look at the change, please? I am not sure if I just need to update the template in the role or if I have to add this new variable to some other file as well. |
Sweet - can your open a PR and we can discuss there? |
Sure. Created #1024 |
Hi i have the same issue. We need to run AWX on kubernetes host with disabled IPv6. |
@derhoeppi Sry but I have no clue how to add this. If you like you can add the needed code to the PR or create another PR to add those parameters. |
I can confirm too, can't deploy 0.24+ (up to 0.28/latest) on a K8s without IPv6 making AWX imposible to upgrade or install. |
Our upgrade from 0.21 to 0.28 also failed from the same reason |
As a quick workarround you could create a configmap "awx-awx-configmap-modified" with the modified https://github.com/ansible/awx-operator/blob/0.29.0/roles/installer/templates/configmaps/config.yaml.j2 and overwrite it within the operator via
|
@mklitzn it looks like you have experience in kubernetes and the deployment of awx. Do you think it is possible to control IPv6 enable / disable in kustomization.yaml? |
Used the workaround mentioned by @mklitzn to fix our deployment. What is the status of the PR from @digifuchsi? That IPv6 change seems to have affected a fair few users and the error is difficult to debug and not immediately obvious. Thanks. |
+1 broken upgrade, as mentioned.. workaround didn't seem to work, 4 me.. |
@kenichimilo It is now possible to disable IPv6 in the nginx config from the AWX CR's spec thanks to this PR: This is currently available in the |
While I appreciate everyone's efforts bringing this project to life and keeping it current, I would be remised if I didn't point out my heartache with this issue. I too came across the IPv6 disabled where awx-web container continually crashes. I eventually (days later) found issue posted and docs. However, the remediation steps of this issue is not clearly defined. How does one implement "Spec: ipv6_disabled: true"? |
this issue is addressed with config:
|
Please confirm the following
Bug Summary
Hi all,
I need to run AWX in an minikube environment with IPv6 disabled.
I can successfully install with awx-operator version <=0.23.0, but starting with version 0.24.0 it fails.
The awx-web container throws an error saying nginx cannot bind to IPv6 (Address family not supported by protocol).
As I cannot find any other issue in the logs I am certain this change is causing the issue. On other IPv6 disabled environments it is showing the same behaviour.
Is it possible to introduce a disable_ipv6 switch so that nginx does not listen to IPv6?
I can try creating a PR on my own if nobody has time to spare and the project would not mind having such a switch.
Thanks
Chris
AWX Operator version
0.24.0
AWX version
21.2.0
Kubernetes platform
minikube
Kubernetes/Platform version
minikube version: v1.25.2 / Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.3"}
Modifications
no
Steps to reproduce
Expected results
AWX is running after some time
Actual results
awx-web container keeps crashing and getting restarted throwing an error that nginx cannot bind to IPv6
Additional information
Operator Logs
No response
The text was updated successfully, but these errors were encountered: