SNMP can be installed in worker nodes when it shall run only in controller nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Enzo Candotti |
Bug Description
Brief Description
SNMP is working fine while running on controller nodes but it can also be installed on worker nodes when it shall not be possible to install in nodes different than controller.
Just to mention that once snmp is installed on worker node, snmp get/walk operations work fine but trap generation is not working.
The SNMP should not be installed on worker nodes.
-----------------
Severity
Minor
-----------------
Steps to Reproduce
1. In STD environment install snmp app
2. Check snmp installation
-----------------
Expected Behavior
SNMP should always be deployed in controllers node
-----------------
Actual Behavior
SNMP is randomly deployed in worker nodes
-----------------
Reproducibility
Intermittent (50% of occurrence)
-----------------
System Configuration
STD lab or VM
2 controllers
2 computes
2 storages.
-----------------
Branch/Pull Time/Commit
SW_VERSION="21.12"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID=
BUILD_DATE=
-----------------
Last Pass
Stx5.0
-----------------
Timestamp/Logs
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-sstem ns-snmp-
-----------------
Alarms
N/A
-----------------
Test Activity
Regression Testing
-----------------
Workaround
No workaround available
Changed in starlingx: | |
assignee: | nobody → Enzo Candotti (ecandotti) |
Changed in starlingx: | |
importance: | Undecided → Low |
Fix proposed to branch: master /review. opendev. org/c/starlingx /snmp-armada- app/+/822711
Review: https:/