Deployment raising a 300.001 port alarm when ovs-dpdk is configured
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
tags: |
added: stx.7.0 removed: stx.6.0 |
Fix proposed to branch: master /review. opendev. org/c/starlingx /config/ +/821827
Review: https:/