"openstack overcloud node provision" sometimes ignores default image
Bug #1851575 reported by
Steve Baker
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Steve Baker |
Bug Description
Setting an 'image' in the 'defaults' of a baremetal provisioning yaml is ignored in some cases, resulting in the hard-coded default image being deployed instead.
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Steve Baker (steve-stevebaker) |
milestone: | none → ussuri-1 |
Changed in tripleo: | |
status: | Triaged → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/692477 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=82f3a35fdce 9a9ab9a63295afa bd91fa7761f60a
Committed: https:/
Submitter: Zuul
Branch: master
commit 82f3a35fdce9a9a b9a63295afabd91 fa7761f60a
Author: Steve Baker <email address hidden>
Date: Fri Nov 1 14:31:10 2019 +1300
Clean up instance defaults setting
This change fixes a problem where an instance entry was not being
populated with an image specified in the defaults dict. This change
sets up a baseline defaults dict before validating the roles, and
populates any instances with the defaults in-place.
Change-Id: I1929e1b135ed53 9a6da09b1ec5d2b 64b6281dc47
Blueprint: nova-less-deploy
Closes-Bug: 1851575