sonic-net / sonic-buildimage

Scripts which perform an installable binary image build for SONiC
Other
722 stars 1.38k forks source link

After enabling and disabling sflow interface, it can't do port breakout. #15248

Open chiourung opened 1 year ago

chiourung commented 1 year ago

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:

  1. config sflow enable
  2. config sflow interface enable Ethernet48
    redis-cli -n 4 keys SFLOW*
    1) "SFLOW_SESSION|Ethernet48"
    2) "SFLOW|global"
    redis-cli -n 4 hgetall "SFLOW_SESSION|Ethernet48"
    1) "admin_state"
    2) "up"
  3. config sflow interface disable Ethernet48
    redis-cli -n 4 hgetall "SFLOW_SESSION|Ethernet48"
    1) "admin_state"
    2) "down"
  4. config interface breakout Ethernet0 4x100G
    
    Do you want to Breakout the port, continue? [y/N]: y

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


#### Describe the results you received:

The sflow design is in conflict with port dependency.

#### Describe the results you expected:

#### Output of `show version`:

(paste your output here)

#### Output of `show techsupport`:

(paste your output here or download and attach the file here )



#### Additional information you deem important (e.g. issue happens only occasionally):

<!--
     Also attach debug file produced by `sudo generate_dump`
-->
judyjoseph commented 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.

chiourung commented 1 year ago

There is an issue when add force option while doing a breakout. https://github.com/sonic-net/sonic-swss/pull/2825