You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that the AWX Operator is open source software provided for free and that I might not receive a timely response.
Bug Summary
Hello All,
We are unable to configure new AWX operator version 2.16.1.
Deployment finishes successfully, however the awx.awx.settings is not picking up the controller username and password.
Tried passing credentials in the playbook as well as directly in the job template(variables), but nothing works.
Error message: "Invalid Authentication Credentials" or "Authentication credentials were not provided"
We can manually login to newly deployed AWX successfully using the same credentials but this module somehow doesn't picks up the credentials.
Note: Everything works in version 2.5.1 or 2.7.1 and awx.awx.settings module doesn't fails with authentication error message.
The issue is observed only in higher version(2.16.1 in our scenario).
We would like to check if we are missing anything pertaining to the module or anything else regarding newer operator version ?
Thank you so much in advance.
AWX Operator version
2.16.1
AWX version
24.3.1
Kubernetes platform
minikube
Kubernetes/Platform version
client: 1.23.2 server: 1.23.3
Modifications
no
Steps to reproduce
Running aws.awx.setting module to configure AWX settings and parameters
It gives authentication error even if required controller credentials are provided.
Expected results
awx.awx.settings should configure AWX related settings.
Actual results
Error message: "Invalid Authentication Credentials" or "Authentication credentials were not provided"
Additional information
No response
Operator Logs
No response
The text was updated successfully, but these errors were encountered:
hey @avijitkulkarni30 this seems like an awx collection issue so we transferred this to the awx repo. can you provide a little more information on how you provide the credentials in your playbook and where you provide them?
can you also provide the awx collection version that is in use as well?
We are providing credentials using lookup plugin in the playbook and fetch them from an external credential manager.
I have also tried to explicitly mention the "controller_username" and "controller_password" as variable during the job template run(variables option in job template) and even in this scenario it fails with same message.
Collection: awx.awx
Version: 24.3.1
Please let me know if any further details required from my end.
Please confirm the following
Bug Summary
Hello All,
We are unable to configure new AWX operator version 2.16.1.
Deployment finishes successfully, however the awx.awx.settings is not picking up the controller username and password.
Tried passing credentials in the playbook as well as directly in the job template(variables), but nothing works.
Error message: "Invalid Authentication Credentials" or "Authentication credentials were not provided"
We can manually login to newly deployed AWX successfully using the same credentials but this module somehow doesn't picks up the credentials.
Note: Everything works in version 2.5.1 or 2.7.1 and awx.awx.settings module doesn't fails with authentication error message.
The issue is observed only in higher version(2.16.1 in our scenario).
We would like to check if we are missing anything pertaining to the module or anything else regarding newer operator version ?
Thank you so much in advance.
AWX Operator version
2.16.1
AWX version
24.3.1
Kubernetes platform
minikube
Kubernetes/Platform version
client: 1.23.2 server: 1.23.3
Modifications
no
Steps to reproduce
Running aws.awx.setting module to configure AWX settings and parameters
It gives authentication error even if required controller credentials are provided.
Expected results
awx.awx.settings should configure AWX related settings.
Actual results
Error message: "Invalid Authentication Credentials" or "Authentication credentials were not provided"
Additional information
No response
Operator Logs
No response
The text was updated successfully, but these errors were encountered: