Traceback in unlock host when configuring pci-passthrough interfaces and sriovdp label enabled

Bug #1856587 reported by Wendy Mitchell on 2019-12-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Medium
Steven Webster

Bug Description

Traceback in unlock attempt after sriovdp added

Severity
--------
Standard

Steps to Reproduce
------------------
1. Configure both controllers with pci-passthrough interfaces
2. Unlock the controllers and confirm they are unlocked, enabled and available before adding the label
Confirm system application-list reports | applied | completed
3. Lock controller-1
4. assign the sriovdp label
$ system host-label-assign controller-1 sriovdp=enabled
5. Attempt to unlock controller-1

Expected Behavior
------------------
Expected to be able to successfully unlock the host with the sriovdp label

Actual Behavior
----------------
Traceback when attempting to unlock node with label added sriovdp=enabled and the unlock fails

[sysadmin@controller-0 log(keystone_admin)]$ system host-label-list controller-1; date
----------------------------------
hostname label key label value

----------------------------------
controller-1 sriovdp enabled

Branch/Pull Time/Commit
-----------------------
2019-12-10_20-00-00

Last Pass
---------
This config was not tested previously

Timestamp/Logs
--------------
see inline

Test Activity
-------------
Regression
----------------------------------
Fri Dec 13 00:58:05 UTC 2019
[sysadmin@controller-0 log(keystone_admin)]$ system application-list
--------------------------------------------------------------------------------------+
application version manifest name manifest file status progress

--------------------------------------------------------------------------------------+
platform-integ-apps 1.0-10 platform-integration-manifest manifest.yaml applied completed

--------------------------------------------------------------------------------------+
[sysadmin@controller-0 log(keystone_admin)]$ system host-unlock controller-1

Traceback (most recent call last):

File "/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/amqp.py", line 437, in _process_data
**args)

File "/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/dispatcher.py", line 172, in dispatch
result = getattr(proxyobj, method)(ctxt, **kwargs)

File "/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py", line 1654, in configure_ihost
self._configure_controller_host(context, host)

File "/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py", line 1319, in _configure_controller_host
self._puppet.update_host_config(host)

File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 30, in _wrapper
func(self, *args, **kwargs)

File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 147, in update_host_config
config.update(puppet_plugin.obj.get_host_config(host))

File "/usr/lib64/python2.7/site-packages/sysinv/puppet/kubernetes.py", line 101, in get_host_config
config.update(self._get_host_pcidp_config(host))

File "/usr/lib64/python2.7/site-packages/sysinv/puppet/kubernetes.py", line 318, in _get_host_pcidp_config
self._get_pcidp_network_resources(),

File "/usr/lib64/python2.7/site-packages/sysinv/puppet/kubernetes.py", line 433, in _get_pcidp_network_resources
constants.INTERFACE_CLASS_PCI_PASSTHROUGH)

File "/usr/lib64/python2.7/site-packages/sysinv/puppet/kubernetes.py", line 369, in _get_pcidp_network_resources_by_ifclass
port = interface.get_sriov_interface_port(self.context, iface)

File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 980, in get_sriov_interface_port
return interface.get_sriov_interface_port(context, iface)

File "/usr/lib64/python2.7/site-packages/sysinv/common/interface.py", line 123, in get_sriov_interface_port
assert iface['ifclass'] == constants.INTERFACE_CLASS_PCI_SRIOV

AssertionError

Reproducibility
---------------
yes

System Configuration
--------------------
HW
(R720 1-2 sriov interface configured + sriov device plugin discovers pci-passthrough interfaces as well)

tags: added: stx.retestneeded
Ghada Khalil (gkhalil) on 2019-12-16
Changed in starlingx:
assignee: nobody → Steven Webster (swebster-wr)
summary: - Traceback in unlock host attempt after sriovdp label added
+ Traceback in unlock host when configuring pci-passthrough interfaces and
+ sriovdp label added
summary: Traceback in unlock host when configuring pci-passthrough interfaces and
- sriovdp label added
+ sriovdp label enabled
tags: added: stx.networking
Ghada Khalil (gkhalil) on 2019-12-16
description: updated
description: updated
Ghada Khalil (gkhalil) wrote :

stx.4.0 / medium priority - currently sriovdp labels are not supported on pci-passthrough interfaces, but should be simple to fix

tags: added: stx.4.0
Changed in starlingx:
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers