quickstart creates oooq_foo flavors which do not match config/node templated names, that fails the overcloud deployment

[Bogdan Dobrelya]

quickstart.sh has option -N to go with pre-created overcloud node configs.

The node configs, like [0] name flavors differently than quickstart creates by default, like oooq_control instead of 'control'.

This makes deployments failing and provides really poor UX :)

To fix the mismatching flavor names, we prolly need to either:
A) rename flavors to oooq_* for all of the config/node files and make disk/vcpu/ram parameters matching the default_disk/default_vcpu/default_memory values.
B) or pick libvirt provisioning defaults, like:

default_disk: 41
default_vcpu: 1
default_memory: 4096

to (hopefully!) fit the smallest flavors pre-created, when undercloud is installed with quickstart using the t-h-t defaults in undercould post install [1]:

openstack flavor list
+--------------------------------------+---------------+------+------+-----------+-------+-----------+
| ID | Name | RAM | Disk | Ephemeral | VCPUs | Is Public |
+--------------------------------------+---------------+------+------+-----------+-------+-----------+
| 490c3578-d2c6-4c02-bf70-d06608e2b0fe | control | 4096 | 40 | 0 | 1 | True |
| 4c5a8cbd-52b1-4cf4-bac9-202a7fb5c00b | compute | 4096 | 40 | 0 | 1 | True |
| 59fbcb8b-bb50-4b4b-bc9c-1167d0850c55 | swift-storage | 4096 | 40 | 0 | 1 | True |
| ba85b168-c2f6-49f6-88d1-41d2dca8e2c9 | block-storage | 4096 | 40 | 0 | 1 | True |
| cf5bfc3b-58f6-4523-a286-447ee735c35e | ceph-storage | 4096 | 40 | 0 | 1 | True |
| d2b5cefb-4535-4a82-aa76-52e725a9dc42 | baremetal | 4096 | 40 | 0 | 1 | True |
+--------------------------------------+---------------+------+------+-----------+-------+-----------+

[0] http://git.openstack.org/cgit/openstack/tripleo-quickstart/tree/config/nodes/1ctlr_1comp.yml#n4
[1] http://git.openstack.org/cgit/openstack/tripleo-heat-templates/tree/extraconfig/post_deploy/undercloud_post.sh#n77

[Bogdan Dobrelya (bogdando)]

Does https://review.openstack.org/#/c/579406 also fix this?..

[Bogdan Dobrelya (bogdando)]

https://bugs.launchpad.net/tripleo/+bug/1790622 looks related, not sure if a dup

[Ronelle Landy (rlandy)]

https://review.openstack.org/#/c/579406 fixed some errors (especially on baremetal/OVB) deployments with nodes not being recognized as suitable hosts, but it does not solve the issue of mismatch control and oooq_control etc. flavors.

[Brendan Shephard (bshephar)]

Is this limited to Quickstart? I'm getting this as of the latest version on a full triple-o deployment using oVirt nodes. I'm unable to specify a flavor or use scheduler hints. Seems regardless what I try, I'm getting the illusive No valid hosts. on overcloud deployment and also hitting this error:

if not alloc_reqs:
150 LOG.info("Got no allocation candidates from the Placement "
151 "API. This could be due to insufficient resources "
152 "or a temporary occurrence as compute nodes start "
153 "up.")
154 raise exception.NoValidHost(reason="")