Cinder setup fails with "The conditional check 'cinder_backend_lvm_inuse | bool' failed"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
High
|
Jesse Pretorius |
Bug Description
Encountered while running setup-infrastru
"TASK [Set default bind mounts] *******
fatal: [r14r730-01]: FAILED! => {"failed": true, "msg": "The conditional check 'cinder_
A very similar issue was reported by lovea in #openstack-ansible here, and he kept better notes than I did:
http://
Note that lovea was re-deploying, I was setting up a fresh environment, and we both experienced this.
Relevant part of my openstack_
```
storage_hosts:
r14r730-01:
ip: 172.29.236.117
container_vars:
cinder_
cinder_
cinder_
lvm:
```
When I commented out the line `iscsi_ip_address: "{{ storage_address }}"`, the playbook completed successfully.
It appears that some of the docs show a default of `iscsi_ip_address: "{{ cinder_
http://
http://
tags: | added: newton-rc-potential |
Changed in openstack-ansible: | |
importance: | Undecided → High |
Changed in openstack-ansible: | |
assignee: | Kevin Carter (kevin-carter) → Michael Carden (mike-carden) |
Changed in openstack-ansible: | |
assignee: | Michael Carden (mike-carden) → nobody |
Changed in openstack-ansible: | |
assignee: | nobody → Kevin Carter (kevin-carter) |
Changed in openstack-ansible: | |
assignee: | Kevin Carter (kevin-carter) → Jesse Pretorius (jesse-pretorius) |
When you commented out the line iscsi_ip_address: "{{ storage_address }}}" , is your cinder.conf properly configured with the proper IP?
It should.
If that's the case, we should just change the doc and tell it's automatically discovered.
We maybe have to test if the precedence of playbooks facts/inventory vars is still fine in the latest version of ansible.
Did you check the resulting cinder.conf file by forcing
iscsi_ip_address: <an ip of your choice, different than the auto-discovered one> ?