Hide Forgot
Description of problem: When attempting node placement via ironic culpabilities and depolyment hints.yaml errors on deploy Version-Release number of selected component (if applicable): python-tripleoclient-5.0.0-0.20160823121648.2a9a168.el7ost.noarch How reproducible:100% Steps to Reproduce: 1.create hints yaml file: parameter_defaults: NovaComputeSchedulerHints: 'capabilities:node': 'novacompute-%index%' ControllerSchedulerHints: 'capabilities:node': 'controller-%index%' 2. set capabilities: ironic node-update 641882f4-f550-4029-9fdc-870e1f28d5f9 replace properties/capabilities='node:controller-0,boot_option:local' ironic node-update ae2afaa5-cde9-4c18-99af-7bc33ecaf588 replace properties/capabilities='node:controller-1,boot_option:local' ironic node-update 503f9fd1-88e6-4b14-8c4c-265687099133 replace properties/capabilities='node:controller-2,boot_option:local' ironic node-update 1237b54b-822e-4eaf-a147-403d53b0e7c1 replace properties/capabilities='node:novacompute-0,boot_option:local' 3. Deploy a HA env with 1 compute Actual results: fails Expected results: compute and controller "instance" bind to the node defined Additional info: from ospd9-->osp10 the format of the string for nova instances changed from "*compute*"-->"*novacompute" The above command set to control node placement works correctly with ospd9, being the only difference is I added "nova" to reflect the new naming convention
Hi! What's the actual failure? If it's "no valid host found", please provide nova-scheduler logs and the command line you used for installation.
I did not save the nova logs and the env is gone. Currently looking for machines to reproduce. But yes, I do believe the error was "no valid host found". The deploy command was: openstack overcloud deploy --templates --neutron-network-type vxlan --neutron-tunnel-types vxlan --control-scale 3 --compute-scale 1 --control-flavor baremetal --compute-flavor baremetal --libvirt-type=kvm --neutron-public-interface=nic2 --timeout=240 -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml -e ~/network-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/scheduler_hints_env.yaml
The command looks ok, will be waiting for the logs.
Please reopen if you find a way to provide nova-scheduler logs. Thanks!
The methodology of binding nodes deploys as expected with Openstack Director 10 rc. keeping status closed