Deployment raising a 300.001 port alarm when ovs-dpdk is configured

Bug #1954908 reported by Andre Kantek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
Medium
Andre Kantek

Bug Description

Brief Description
-----------------
It was detected the alarm 300.001 with the cause "Port XXXX on DB is no longer reported by the OS" if the interface might be owned by a userspace poll mode driver like ovs-dpdk

After the interface configuration to class "data" and usage in ovs-dpdk it will no longer be available to the host OS and a report gathered by sysinv-agent will not contain it. This will be handled as an alarm since now sysinv-conductor now matches the reported ports with current database

Severity
--------
<Minor: System/Feature is usable with minor issue>

Steps to Reproduce
------------------
configure ovs-dpdk and attach ports to it

Expected Behavior
------------------
No alarm raised

Actual Behavior
----------------
alarm 300.001 is raised

Reproducibility
---------------
Reproducible

System Configuration
--------------------
Simplex systems

Test Activity
-------------
Sanity

Workaround
----------
Alarm can be ignored/deleted as it is not affecting operation

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/config/+/821827

Changed in starlingx:
status: New → In Progress
Revision history for this message
Ghada Khalil (gkhalil) wrote (last edit ):

screening: stx.7.0 / low - issue related to stx.6.0 feature: https://storyboard.openstack.org/#!/story/2009112
However, this is just an alarm and can be manually deleted, so will not hold up stx.6.0. Fix should go in stx master only.

Changed in starlingx:
importance: Undecided → Medium
assignee: nobody → Andre Kantek (akantek)
tags: added: stx.6.0 stx.networking
Ghada Khalil (gkhalil)
tags: added: stx.7.0
removed: stx.6.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (master)

Reviewed: https://review.opendev.org/c/starlingx/config/+/821827
Committed: https://opendev.org/starlingx/config/commit/0d2b4c21062d049a478934ad9701491a205eda64
Submitter: "Zuul (22348)"
Branch: master

commit 0d2b4c21062d049a478934ad9701491a205eda64
Author: Andre Fernando Zanella Kantek <email address hidden>
Date: Wed Dec 15 06:46:11 2021 -0500

    Do not raise alarm if data interface is not reported by the OS

    It was detected the alarm 300.001 raised if a DATA interface is owned
    by a userspace poll mode driver like ovs-dpdk and no longer be
    reported by the OS

    This is not an alarm situation, the interface is just not available
    to the host OS, so for this case it will not be raised

    Test plan
    PASS pci-sriov are not removed from Linux with ovs-dpdk
    PASS data interface are removed from Linux with ovs-dpdk

    Closes-bug: 1954908

    Signed-off-by: Andre Fernando Zanella Kantek <email address hidden>
    Change-Id: Iaba6c1a2b1d0523816ed01d89519a878901d4dbf

Changed in starlingx:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.