Merged
Conversation
Bumps [ansible](https://github.com/ansible-community/ansible-build-data) from 11.2.0 to 12.2.0. - [Changelog](https://github.com/ansible-community/ansible-build-data/blob/main/docs/release-process.md) - [Commits](ansible-community/ansible-build-data@11.2.0...12.2.0) --- updated-dependencies: - dependency-name: ansible dependency-version: 12.2.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
Contributor
|
The ERROR: Cannot install -r requirements.txt (line 1) and ansible-core==2.18.2 because these package versions have conflicting dependencies.
The conflict is caused by:
The user requested ansible-core==2.18.2
ansible 12.2.0 depends on ansible-core~=2.19.4
Another noteworthy mention is that Ansible v12 introduces stricter terms for the use of conditionals (e.g. explicit evaluation to return a boolean). TASK [Set async_dir for HOME env] **********************************************
[ERROR]: Task failed: Conditional result (True) was derived from value of type 'str' at "<environment variable 'HOME'>". Conditionals must have a boolean result.
Task failed.
Origin: /Users/etepsic/.pyenv/versions/3.12.3/envs/graylog-ansible-role/lib/python3.12/site-packages/molecule_plugins/docker/playbooks/destroy.yml:10:7
8 - always
9 tasks:
10 - name: Set async_dir for HOME env
^ column 7
<<< caused by >>>
Conditional result (True) was derived from value of type 'str' at "<environment variable 'HOME'>". Conditionals must have a boolean result.
Origin: /Users/etepsic/.pyenv/versions/3.12.3/envs/graylog-ansible-role/lib/python3.12/site-packages/molecule_plugins/docker/playbooks/destroy.yml:13:13
11 ansible.builtin.set_fact:
12 ansible_async_dir: "{{ lookup('env', 'HOME') }}/.ansible_async/"
13 when: (lookup('env', 'HOME'))
^ column 13
Broken conditionals can be temporarily allowed with the `ALLOW_BROKEN_CONDITIONALS` configuration option.
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Task failed: Conditional result (True) was derived from value of type 'str' at \"<environment variable 'HOME'>\". Conditionals must have a boolean result."}
PLAY RECAP *********************************************************************
Adding the following workaround to provisioner:
name: ansible
config_options:
defaults:
ALLOW_BROKEN_CONDITIONALS: true
|
…thy boolean conditional in Ansible v12
…d destroy.yml playbook use of broken conditional
….yml playbook use of broken conditional
Contributor
|
After further review, it was found that an older version of molecules-plugin was responsible for the use of broken conditionals in the Docker playbook. Upgrading the molecule-plugins python package to the latest release resolved the deprecation error. The molecule package version was also updated from 25.1.0 to 26.3.0, which then required ansible-compat to be upgraded from 25.1.2 to 25.1.4. |
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
1 participant
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.
Bumps ansible from 11.2.0 to 12.2.0.
Commits
ff7b95bAnsible 12.2.0: Dependencies, changelog and porting guide (#621)21dc7c1Remove deprecated community.digitalocean from Ansible 13.0.0b1. (#620)4dc8c5eAnsible 13.0.0a5: Dependencies, changelog and porting guide (#619)6fda54dBump actions/upload-artifact from 4 to 5 (#617)8ad093eBump actions/download-artifact from 5 to 6 (#616)e3f1851Ansible 13.0.0a4: Dependencies, changelog and porting guide (#615)daac485Bump wntrblm/nox from 2025.05.01 to 2025.10.16 (#614)65d2b26Ansible 13.0.0a3: Dependencies, changelog and porting guide (#613)ed34a59Revert "Restrict ibm.storage_virtualize to < 3.1.0. (#608)" (#612)d5be323Ansible 13.0.0a2: Dependencies, changelog and porting guide (#611)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.