Predictable baremetal node placement using 'profile' does not work

Bug #1918359 reported by Harald Jensås
6
This bug affects 1 person
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/baremetal_deployment.yaml
- 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-54350-leaf1-0 -f yaml -c properties
                                                                                                                                        properties:
  capabilities: profile:control,boot_option:local
  cpu_arch: x86_64
  cpus: '4'
  local_gb: '49'
  memory_mb: '8192'
  vendor: unknown

$ baremetal node show baremetal-54350-leaf2-0 -f yaml -c properties
properties:
  capabilities: profile:compute-leaf2,boot_option:local
  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-75d1-4438-abc1-0e2c356b0201 | baremetal-54350-leaf1-0 | 4716b5b3-4cd9-432d-b87d-e48cf00d83ee | compute-0 | ACTIVE | ctlplane=192.168.25.21 |
| 265b2519-0886-486d-8246-66572fefaf04 | baremetal-54350-leaf2-0 | 1ec9fa91-3164-4361-8d75-cd4613e0eac4 | controller-0 | ACTIVE | ctlplane=192.168.26.20 |
+--------------------------------------+-------------------------+--------------------------------------+--------------+--------+------------------------+

Changed in tripleo:
milestone: wallaby-3 → wallaby-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-ansible 3.1.0

This issue was fixed in the openstack/tripleo-ansible 3.1.0 release.

Changed in tripleo:
milestone: wallaby-rc1 → xena-1
Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.