Fix Ansible Deployments #373
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Ansible deployments are failing because of a faulty config. We first noticed it on GP, so this PR fixes it to avoid running into the same error.
The version of Django is also updated to the latest.
More on the failure and fix
cd deploy/ && ansible-playbook deploy.yml -l staging -e k8s_container_image_tag=develop-tag#Warning: : Deprecation warnings can be disabled by settingdeprecation_warnings=Falsein ansible.cfg. [DEPRECATION WARNING]: DEFAULT_UNDEFINED_VAR_BEHAVIOR option. Reason: This option is no longer used in the Ansible Core code base. Alternatives: There is no alternative at the moment. A different mechanism would have to be implemented in the current code base. This feature will be removed from ansible-core version 2.23.Error: : The 'community.general.yaml' callback plugin has been removed. The plugin has been superseded by the option
result_format=yamlin callback plugin ansible.builtin.default from ansible-core 2.13 onwards. This feature was removed from collection 'community.general' version 12.0.0.Error: Process completed with exit code 1.
https://forum.ansible.com/t/ansible-yaml-output-community-general-yaml-has-been-deprecated/39480/9
and
https://docs.ansible.com/projects/ansible/latest/collections/ansible/builtin/default_callback.html#parameter-result_format
Removing
error_on_undefined_varsto quiet the deprecation warning, since it isn't supported any more.