Predictable baremetal node placement using 'profile' does not work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Harald Jensås |
Bug Description
Using 'profile' for predictable placement does not work whendeploying baremetal.
(undercloud) [centos@undercloud ~]$ cat overcloud/
- name: Controller
count: 1
hostname_format: controller-%index%
defaults:
profile: control
- name: Compute
count: 1
hostname_format: compute-%index%
defaults:
profile: compute-leaf2
$ baremetal node show baremetal-
capabilities: profile:
cpu_arch: x86_64
cpus: '4'
local_gb: '49'
memory_mb: '8192'
vendor: unknown
$ baremetal node show baremetal-
properties:
capabilities: profile:
cpu_arch: x86_64
cpus: '4'
local_gb: '49'
memory_mb: '8192'
vendor: unknown
(undercloud) [centos@undercloud ~]$ metalsmith list
+------
| UUID | Node Name | Allocation UUID | Hostname | State | IP Addresses |
+------
| b819c229-
| 265b2519-
+------
Changed in tripleo: | |
milestone: | wallaby-3 → wallaby-rc1 |
Changed in tripleo: | |
milestone: | wallaby-rc1 → xena-1 |
Changed in tripleo: | |
status: | Triaged → Fix Released |
This issue was fixed in the openstack/ tripleo- ansible 3.1.0 release.