-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
None
-
None
-
False
-
-
False
-
?
-
None
-
-
-
Important
According to this documentation the dmiString must be taken into account when the nodeset is depoyed. However, having a configuration like this:
edpm_network_config_os_net_config_mappings:
edpm-compute-0:
dmiString: system-serial-number
id: 1LDXXXX
...
edpm-compute-1:
dmiString: system-serial-number
id: HBVXXXX
...
After the nodeset is deployed we can see the that dmiString seems to be ignored:
[cloud-admin@compute-0 ~]$ sudo dmidecode -s system-serial-number HBVXXXX [cloud-admin@compute-1 ~]$ sudo dmidecode -s system-serial-number 1LDXXXX
Although we can see the theoretically correct configuration in the last applied configuration:
[zuul@controller-0 ~]$ oc get osdpns openstack-edpm -ojson |jq .metadata.annotations
{
"kubectl.kubernetes.io/last-applied-configuration": "{\"apiVersion\":\"dataplane.openstack.org/v1beta1\",\"kind\":\"OpenStackDataPlaneNodeSet\",\"metadata\":{\"annotations\":{},\"name\":\"openstack-edpm\",...{\"edpm-compute-0\":{\"dmiString\":\"system-serial-number\",\"id\":\"1LDXXX\",...,\"edpm-compute-1\":{\"dmiString\":\"system-serial-number\",\"id\":\"HBVXXXX\",...}}\n"
}
