-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error TASK [libvirt : Create libvirt networks] #1128
Comments
@asalkeld Hmm this normally happens when there's an error in the j2 template but I don't think anything changed in that area (the metal3-dev-env version we use is pinned ref https://github.com/openshift-metal3/dev-scripts/blob/master/01_install_requirements.sh#L22) I wonder if this is related to the ansible version - what version are you using? |
ansible --version |
Ok not the ansible version, looks the same as my environment. I suspect the assisted install changed the environment in some way that's altered the variables input to the j2 templating - probably the easiest way to debug is hack https://github.com/metal3-io/metal3-dev-env/blob/master/vm-setup/roles/libvirt/tasks/network_setup_tasks.yml#L34 to move the If you can dump the vars consumed in the template as a task that may also show us what the difference is. |
Ok having debugged in the environment provided by @asalkeld I discovered this is caused by an old version of python-jinja2:
It seems something pip installed an old 2.7.2 version, which lacks namespace support (added in 2.10) so this part of the templating breaks: Unfortunately the error generated isn't super clear, and evidently we're lacking sufficient validation of the required version. Looking at the logs it seems that ansible/jinja2 was already installed on the first run of |
I am not sure @hardys it must have been pulled in as a dep. I'll keep an eye on it. |
Describe the bug
I am trying to bring up a cluster and keep getting the below anisble error when runing "TASK [libvirt : Create libvirt networks]".
To Reproduce
Note: I have had an assisted-installer cluster on this machine before (but ran a "make destoy" in that repo first).
My config.sh has the following set
CI_TOKEN
PERSONAL_PULL_SECRET
OPENSHIFT_RELEASE_TYPE=ci
I ran
observed behavior
The text was updated successfully, but these errors were encountered: