undercloud deployment fails

[Matthias Runge]

I'm using devmode:

bash devmode.sh --no-gate --ovb -d -w /var/tmp/tripleo_local

2017-12-18 13:50:49 | Complete!
2017-12-18 13:50:49 | + '[' -d /home/stack/clapper ']'
2017-12-18 13:50:49 | + git clone https://github.com/rthallisey/clapper.git /home/stack/clapper
2017-12-18 13:50:49 | Cloning into '/home/stack/clapper'...
2017-12-18 13:50:51 | ++ python /home/stack/clapper/instackenv-validator.py -f /home/stack/instackenv.json
2017-12-18 13:50:51 | INFO:__main__:Checking node 10.0.1.9
2017-12-18 13:50:51 | DEBUG:__main__:Identified baremetal node
2017-12-18 13:50:51 | DEBUG:__main__:Executing: ipmitool -R 1 -I lanplus -H 10.0.1.9 -U admin -P password chassis status
2017-12-18 13:50:53 | Error: Unable to establish IPMI v2 / RMCP+ session
2017-12-18 13:50:53 | ERROR:__main__:ERROR: ipmitool failed
2017-12-18 13:50:53 | INFO:__main__:Checking node 10.0.1.4
2017-12-18 13:50:53 | DEBUG:__main__:Identified baremetal node
2017-12-18 13:50:53 | DEBUG:__main__:Executing: ipmitool -R 1 -I lanplus -H 10.0.1.4 -U admin -P password chassis status
2017-12-18 13:50:55 | Error: Unable to establish IPMI v2 / RMCP+ session
2017-12-18 13:50:55 | ERROR:__main__:ERROR: ipmitool failed
2017-12-18 13:50:55 | DEBUG:__main__:Baremetal IPs are all unique.
2017-12-18 13:50:55 | DEBUG:__main__:MAC addresses are all unique.
2017-12-18 13:50:55 | + export 'IPMI_VALIDATE=
2017-12-18 13:50:55 | --------------------
2017-12-18 13:50:55 | FAILURE: instackenv validator found 2 errors
2017-12-18 13:50:55 | Failure to contact below addresses
2017-12-18 13:50:55 | IPMI Address : 10.0.1.9
2017-12-18 13:50:55 | IPMI Address : 10.0.1.4'
2017-12-18 13:50:55 | + IPMI_VALIDATE='
2017-12-18 13:50:55 | --------------------
2017-12-18 13:50:55 | FAILURE: instackenv validator found 2 errors
2017-12-18 13:50:55 | Failure to contact below addresses
2017-12-18 13:50:55 | IPMI Address : 10.0.1.9
2017-12-18 13:50:55 | IPMI Address : 10.0.1.4'
2017-12-18 13:50:55 | + [[
2017-12-18 13:50:55 | --------------------
2017-12-18 13:50:55 | FAILURE: instackenv validator found 2 errors
2017-12-18 13:50:55 | Failure to contact below addresses
2017-12-18 13:50:55 | IPMI Address : 10.0.1.9
2017-12-18 13:50:55 | IPMI Address : 10.0.1.4 != *SUCCESS* ]]
2017-12-18 13:50:55 | + echo 'instackenv.json did not validate.'
2017-12-18 13:50:55 | instackenv.json did not validate.
2017-12-18 13:50:55 | + echo -------------------- FAILURE: instackenv validator found 2 errors Failure to contact below addresses IPMI Address : 10.0.1.9 IPMI Address : 10.0.1.4
2017-12-18 13:50:55 | -------------------- FAILURE: instackenv validator found 2 errors Failure to contact below addresses IPMI Address : 10.0.1.9 IPMI Address : 10.0.1.4
2017-12-18 13:50:55 | + exit 1

The overcloud machines don't even get the address added:

openstack server show 90-mrunge--baremetal_1 | grep addresses
| addresses | 90-mrunge--public=10.0.0.4, 10.0.0.13; 90-mrunge--overcloud_storage_net=172.18.0.10; 90-mrunge--overcloud_internal_net=172.17.0.9; 90-mrunge--overcloud_storage_mgmt_net=172.19.0.7; 90-mrunge--overcloud_tenant_net=172.16.0.2; 90-mrunge--provision=192.168.24.5 |

[Gabriele Cerami (gcerami)]

This error occurs when using --ovb, but pointing to a different openstack instance than rdocloud.

[Matthias Runge (mrunge)]

Since rdo-cloud has not enough resources available for me to test, is this somehow reproducible somewhere else?

[Matthias Runge (mrunge)]

the baremetal instances don't pick up IPs from private network, but are getting two from public net instead.

The bmc instance instead is deployed on the private network.

[Matthias Runge (mrunge)]

update on this, rdo-cloud behaves exactly the same for me

[Matthias Runge (mrunge)]

gets stranger: While I could reproduce the issue on rdo-cloud, I can not anymore on my local env here.

[Matthias Runge (mrunge)]

Haven't seen this for a while now, can not reproduce anymore. Removing milestone, assignee etc. to get this expunged.