Closed borisno2 closed 7 years ago
Howdy, and thank you for the bug report! The --debug
build output that's requested would include the resultant playbook in applying that role (see: https://github.com/ansible/ansible-container/blob/1c636ad/container/core.py#L512-L513). It would be immensely helpful to trying to help solve this problem if you could share the build output, especially those debug lines for the role that misbehaved.
@chouseknecht I'm 90% sure the reason this is happening is that the generated playbook doesn't include the variablespace, so no variables are defined for the condition to evaluate. But I'd love to make sure.
Thanks @j00bar Full output of build command with debug is here https://gist.github.com/borisno2/692adc04c8874b0a9ffe68d09a5e0325 It looks like, once I fixed up a few things in the role it did in fact skip each individual task within the demo role. I would have expected it to not even look at the role (I think this is what it did previously).
@borisno2
I'm trying to recreate this scenario. Where does edx_install_demo
get defined? It's not in the defaults
section of container.yml
. Is it passed in via --var-file
?
@chouseknecht:
same behavior (0.9.2) but specific to import_role/include_role
(and conditional applied to meta/main.yml
dependencies)
ISSUE TYPE
container.yml
OS / ENVIRONMENT
SUMMARY
STEPS TO REPRODUCE
when
tags seam to be ignored when used in roles. In the below example the demo role is installed even when the variableedx_install_demo
is not set or is set tofalse
EXPECTED RESULTS
The demo role should be skipped.
ACTUAL RESULTS
The demo role was installed.