Saikrishna Arcot

Looks like there are some test failures related to the changes here. Also, I tested the current changes on a multi-ASIC KVM, and while it looks like containercfgd in a...

Yes, I pulled in all 3 PRs in my test image, built a multi-ASIC image, loaded it, enabled the rate-limit feature, and changed the rate limiting: ``` admin@vlab-08:~$ sudo config...

/azpw run Azure.sonic-buildimage

Looks like there's a new loganalyzer error message on t0: ``` Apr 8 07:23:49.040082 vlab-01 ERR sfputil: Failed to instantiate Chassis due to FileNotFoundError('Metadata file /etc/sonic/vs_chassis_metadata.json not found') ``` Is...

@deepak-singhal0408 use `/azpw` instead of `/azp`.

I don't think `rfkill` is actually needed on any network switch, since this is usually used as a kill switch for wifi and bluetooth devices, and `cfg80211` is only for...

Has/will this been upstreamed?

> Yes, once the PR is reviewed and approved it should automatically get merged to master (upstream) I am sure you know that process.So I really don’t completely understand your...

Sorry for the delay here, could you rebase your changes on top of the master branch, or merge in the current master branch into your branch? This is to resolve...

I think the fallback LAG feature described [here](https://github.com/sonic-net/SONiC/blob/master/doc/lag/LACP%20Fallback%20Feature%20for%20SONiC_v0.5.md) does the same thing basically, except that it allows LACP to be established once the peer device is in a state to...