Closed madchap closed 6 years ago
@ctrlaltdel is it possible you introduced the bug in commit d5a26122cf8077fe1dc39ee9e17ffd47e70581c7 ??
if NAME
is not defined then the default is missing ?
Also, we can reference the value like "{{ name }}"
Can we change:
- net-name: "{{ lookup('env', 'NETWORK') | default(lookup('env', 'NAME'), true) }}"
with:
- net-name: "{{ lookup('env', 'NETWORK') | default(name, true) }}"
@madchap if you can test the proposed change please give feedback, or even better propose a PR
Yeah, my bad! I'm currently re-working how these variables are being set because it's quite messy for now.
All the defaults will be set in group_vars/all.yaml
instead of being scattered all around.
OK, If you want me to test a refactory branch let me know.
@zioproto yep, it's available there: https://github.com/infraly/k8s-on-openstack/tree/refactor
@madchap Hopefully, it will be fixed next time you'll give it a try :)
@ctrlaltdel are a workaround lets just revert commit d5a2612 and lets close this issue
Hopefully now fixed on master, happy testing!
Hi @ctrlaltdel :)
Thanks a lot for the job!
I tried to run it quickly before getting some zzzz. So before I forget, and maybe I am lucky not to say too many dumb things at this time...
I tried a minimal setup, where on top of the regular OS_* which get populated upon my cli login (v3), I have put:
My deployment bombs at
Looking at the code (specifically at roles/openstack-master/tasks/main.yaml), the default for NETWORK is
k8s
, which indeed does not exist in my tenant. However, previous ansible steps do create a network for me, which seems to be derived from NAME.Not digging much further, shouldn't the NETWORK variable get its value from the NAME variable in that case?
Thanks, see you.