Unlock failed because vlan id of oam interface is none
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Joohyun |
Bug Description
Brief Description
-----------------
When configuring an interface to vlan, it is possible to configure the interface without entering a vlan id.
If vlan id is set without input, vlan id is set to NONE. If this interface is assigned to oam and unlocked, a problem occurs. After unlock, the device name is set to vlanNone and the oam interface cannot up normally.
Severity
--------
Major
Steps to Reproduce
------------------
1. create vlan interface without vlan id
2. assign to oam
3. unlock
Expected Behavior
------------------
If configuring an interface to vlan, it must to enter vlan id.
Actual Behavior
----------------
When configuring an interface to vlan, it is possible to configure the interface without entering a vlan id.
Reproducibility
---------------
100%
System Configuration
-------
All
Branch/Pull Time/Commit
-------
N/A
Last Pass
---------
N/A
Timestamp/Logs
--------------
N/A
Test Activity
-------------
Sanity
Workaround
----------
N/A
tags: | added: stx.networking |
tags: | added: stx.7.0 |
Changed in starlingx: | |
importance: | Undecided → Medium |
assignee: | nobody → Joohyun (ohjoohyun) |
Fix proposed to branch: master /review. opendev. org/c/starlingx /config/ +/846903
Review: https:/