Passwords with some special characters cause issues

[kurokobo]

Passwords with some special characters cause issues

[KlutzyBubbles]

Thanks for updating, as a workaround, I've add note for usable letteres in password:

Note that some special charactors like &, $, etc. in password under awx-postgres-configuration might cause the deployment issue. Not tested all charactors, but ! is safe to use at least.
https://github.com/kurokobo/awx-on-k3s#prepare-required-files

From my pain the past few days it seems . cant be used either.

[kurokobo]

Thanks, I've never know that and confirmed that this is reproducible on my side.

This behavior came with this line; the password will be passed without quoting.

The awx-operator documentation says that if the password has special characters it should be quoted.

True. But I believe this was probably added without testing. If the password was quoted, the DB will be initialized with the password including quote charactors, it will be unquoted during deployment tasks by AWX side, so I beleave the AWX can't connect DB in the first place due to wrong password due to missing quotes.

Therefore, the password should not be quoted by user, but shoud be quoted by Operator. This is an issue of Operator, so new issue on Operator's repository should be created.

Of course I can, but if you like, you can create an issue of this matter in Operator's repository.

[seadoox]

Go ahead if you don't mind. Thank you for all of your effort on this project! It is super helpful.

…

On Fri, Mar 11, 2022, 7:05 AM kurokobo ***@***.***> wrote: Thanks, I've never know that and confirmed that this is reproducible on my side. This behavior came with this line; the password will be passed without quoting <https://github.com/ansible/awx-operator/blob/5375fec77d02fec5d0763a5910a643bec6eeb32f/roles/backup/tasks/postgres.yml#L102> . The awx-operator documentation says that if the password has special characters it should be quoted. True. But I believe this was probably added without testing. If the password was quoted, it will be quoted twice in credentials.py <https://github.com/ansible/awx-operator/blob/5375fec77d02fec5d0763a5910a643bec6eeb32f/roles/installer/templates/credentials.py.j2#L7>, so I beleave the AWX can't connect DB in the first place due to wrong password which includes quotes. Therefore, the password should not be quoted by user, but shoud be quoted by Operator. This is an issue of Operator, so new issue on Operator's repository should be created. Of course I can, but if you like, you can create an issue of this matter in Operator's repository. — Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKB4PH3HUMP525TISGFVSDU7NAKFANCNFSM5QNR4SMQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[kurokobo]

Thanks for updating, as a workaround, I've add note for usable letteres in password:

Note that some special charactors like &, $, etc. in password under awx-postgres-configuration might cause the deployment issue. Not tested all charactors, but ! is safe to use at least.
https://github.com/kurokobo/awx-on-k3s#prepare-required-files

[kurokobo]

@seadoox @KlutzyBubbles
Just for your information, I made a PR ansible/awx-operator#838 for this issue for the upstream, and the PR had released with 0.19.0.
I've confirmed that the issue solved with Operator 0.19.0 on my side.