Open chiourung opened 1 year ago
@chiourung Since the sflow config is not removed explicitly, you will have to use force option while doing a break out. This error is expected. Please check and get back.
There is an issue when add force option while doing a breakout. https://github.com/sonic-net/sonic-swss/pull/2825
Description
After enabling sflow interface, it can't remove the port configuration from the CLI. And then it can't do port breakout for the port.
Steps to reproduce the issue:
Running Breakout Mode : 1x100G40G Target Breakout Mode : 4x100G
Ports to be deleted : { "Ethernet0": "100000" } Ports to be added : { "Ethernet0": "100000", "Ethernet2": "100000", "Ethernet4": "100000", "Ethernet6": "100000" }
After running Logic to limit the impact
Final list of ports to be deleted : { "Ethernet0": "100000" } Final list of ports to be added : { "Ethernet0": "100000", "Ethernet2": "100000", "Ethernet4": "100000", "Ethernet6": "100000" } sonic_yang(6):Note: Below table(s) have no YANG models: CONSOLE_SWITCH, DHCP_SERVER, RESTAPI, SNMP, SNMP_COMMUNITY, XCVRD_LOG Dependecies Exist. No further action will be taken Printing dependecies /sonic-sflow:sonic-sflow/SFLOW_SESSION/SFLOW_SESSION_LIST[port='Ethernet0']/port
(paste your output here)
(paste your output here or download and attach the file here )