Description of problem: I ommitted a few fields from the nodes in instackenv.json, such as number of cpus and memory, and ran the command "instack-ironic-deployment --nodes-json instackenv.json --register-nodes". The command exited silently without any errors (apart from the non-zero exit status). It's important that the user get a clear failure reason and know that the operation failed. Version-Release number of selected component (if applicable): instack-0.0.6-1.el7ost.noarch instack-undercloud-2.1.1-dev14.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. Use a sample instackenv.json file such as http://file.tlv.redhat.com/~ukalifon/instackenv.json 2. Delete some of the fields in one of the nodes, such as the number of cpus or memory 3. Run "instack-ironic-deployment --nodes-json instackenv.json --register-nodes" Actual results: No error message
for those that have this problem and are trying to get to the server which i suspect is internal, there is another sample online at https://www.rdoproject.org/Instack_FAQ#What_is_the_NODES_JSON_file_format.3F oh and it also affects rhosp director 7
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.