Openstack compute labels assigned to worker nodes by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
David Sullivan |
Bug Description
Brief Description
-----------------
I did not assign the openstack compute labels to a worker node.
Severity
--------
Critical, system not useable for non-openstack worker nodes
Steps to Reproduce
------------------
Install and provision a worker node without assigning the openstack compute labels. Unlock worker nodes
Expected Behavior
------------------
Openstack compute labels were not assigned
Actual Behavior
----------------
Openstack compute labels are assigned
Reproducibility
---------------
100%
System Configuration
-------
Standard system
Branch/Pull Time/Commit
-------
19.01
2019-04-05 20:23:11 -0400
Last Pass
---------
Suspect never
Timestamp/Logs
--------------
Problem code is here
sysinv/
def _process_
# Node labels are host personality based and are defined in
# metadata.yaml file in the following format:
# labels:
# controller: '<label-
# compute: '<label-
...
# Add the default labels for system app. They must exist for
# the app manifest to be applied successfully. If the nodes have
# been assigned these labels manually before, these
# reassignments are simply ignored.
if app.system_app:
Test Activity
-------------
Other
Changed in starlingx: | |
importance: | Undecided → Critical |
tags: | added: stx.config |
Changed in starlingx: | |
importance: | Critical → High |
Marking as release gating; should be addressed asap as it prevents the use of a containerized env without openstack.