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
Running the ansible module panos_active_in_ha in a playbook we get errors generated by the script:
/usr/local/lib/python3.9/site-packages/panos_upgrade_assurance/check_firewall.py, line 109 (locale.setlocale)
It is referencing for a locale code from:
/usr/lib64/python3.9/locale.py", line 610
But errors with this:
setlocale(category, locale)\nlocale.Error: unsupported locale setting\n"
We have looked in the /usr/lib64/python3.9/locale.py in the execution environment, the section that is reporting back to check_firewall.py is:
if locale and not isinstance(locale, _builtin_str):
# convert to string
locale = normalize(_build_localename(locale))
return _setlocale(category, locale)
And we can see the default locale from check_firewall.py listed as a locale in locale.py
The locale of execution environment is: LANG=C.utf8 (which is in locale.py, but all lower case (if that is an issue))
Expected behavior
To use the default locale as expected
Current behavior
Playbook fails with this error
"/tmp/ansible_paloaltonetworks.panos.panos_active_in_ha_payload_87h9q4vv/ansible_paloaltonetworks.panos.panos_active_in_ha_payload.zip/ansible_collections/paloaltonetworks/panos/plugins/modules/panos_active_in_ha.py", line 125, in main\n File "/usr/local/lib/python3.9/site-packages/panos_upgrade_assurance/check_firewall.py", line 109, in init\n locale.setlocale(\n File "/usr/lib64/python3.9/locale.py", line 610, in setlocale\n return _setlocale(category, locale)\nlocale.Error: unsupported locale setting\n",
"msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
Possible solution
Unsure
Steps to reproduce
Our requirements.txt for the ansible-builder application are the below, we are installing all
Describe the bug
Running the ansible module panos_active_in_ha in a playbook we get errors generated by the script:
/usr/local/lib/python3.9/site-packages/panos_upgrade_assurance/check_firewall.py, line 109 (locale.setlocale)
It is referencing for a locale code from:
/usr/lib64/python3.9/locale.py", line 610
But errors with this:
setlocale(category, locale)\nlocale.Error: unsupported locale setting\n"
We have looked in the /usr/lib64/python3.9/locale.py in the execution environment, the section that is reporting back to check_firewall.py is:
if locale and not isinstance(locale, _builtin_str):
# convert to string
locale = normalize(_build_localename(locale))
return _setlocale(category, locale)
And we can see the default locale from check_firewall.py listed as a locale in locale.py
The locale of execution environment is: LANG=C.utf8 (which is in locale.py, but all lower case (if that is an issue))
Expected behavior
To use the default locale as expected
Current behavior
Playbook fails with this error
"/tmp/ansible_paloaltonetworks.panos.panos_active_in_ha_payload_87h9q4vv/ansible_paloaltonetworks.panos.panos_active_in_ha_payload.zip/ansible_collections/paloaltonetworks/panos/plugins/modules/panos_active_in_ha.py", line 125, in main\n File "/usr/local/lib/python3.9/site-packages/panos_upgrade_assurance/check_firewall.py", line 109, in init\n locale.setlocale(\n File "/usr/lib64/python3.9/locale.py", line 610, in setlocale\n return _setlocale(category, locale)\nlocale.Error: unsupported locale setting\n",
"msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
Possible solution
Unsure
Steps to reproduce
Our requirements.txt for the ansible-builder application are the below, we are installing all
scp
pyats
ansible-pylibssh
ntc-templates
netmiko
paramiko
pan-os-python
pan-python
pandevice
panos-upgrade-assurance
We are installing these collections:
collections:
The execution environment is based from the latest EE_BASE_IMAGE each time
EE_BASE_IMAGE: quay.io/ansible/awx-ee:latest
Context
We are trying to use the panos_active_in_ha.py module to be able to force sync config from the active firewall in a HA Pair
Your Environment
Enough info should be detailed above. We are using AWX on a single node kubernetes environment
The text was updated successfully, but these errors were encountered: