Comment 0 for bug 1823705

Revision history for this message
Brent Rowsell (brent-rowsell) wrote :

Brief Description
-----------------
I did not assign the openstack compute labels to a worker node. After

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/conductor/kube_app.py

    def _process_node_labels(self, app, op=constants.LABEL_ASSIGN_OP):
        # Node labels are host personality based and are defined in
        # metadata.yaml file in the following format:
        # labels:
        # controller: '<label-key1>=<value>, <label-key2>=<value>, ...'
        # compute: '<label-key1>=<value>, <label-key2>=<value>, ...'

...

# 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:
            controller_labels_set.add(constants.CONTROL_PLANE_LABEL)
            compute_labels_set.add(constants.COMPUTE_NODE_LABEL)
            compute_labels_set.add(constants.OPENVSWITCH_LABEL)
            compute_labels_set.add(constants.SRIOV_LABEL)

Test Activity
-------------
Other