Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dvs] Re-add runcmd_async command #1508

Merged
merged 1 commit into from
Nov 18, 2020
Merged

[dvs] Re-add runcmd_async command #1508

merged 1 commit into from
Nov 18, 2020

Conversation

daall
Copy link
Contributor

@daall daall commented Nov 18, 2020

Signed-off-by: Danny Allen daall@microsoft.com

What I did
Re-added the runcmd_async method that was removed in a recent refactor.

Why I did it
The buildimage tests depend on this command to work properly.

How I verified it

Details if related

Signed-off-by: Danny Allen <daall@microsoft.com>
@daall daall merged commit 5ba548c into sonic-net:master Nov 18, 2020
@daall daall deleted the cmd_asyncd branch November 18, 2020 23:07
daall added a commit to daall/sonic-swss that referenced this pull request Dec 7, 2020
Signed-off-by: Danny Allen <daall@microsoft.com>
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
- What I did
Prevent errors in the log when PFCWD starts on ports that PFC was not previously enabled.

Example of such errors in the log:
Nov 13 17:27:22.878468 arc-switch1038 ERR swss#orchagent: :- createEntry: Failed to start PFC Watchdog on port Ethernet100
Nov 13 17:27:23.878620 arc-switch1038 NOTICE swss#orchagent: :- registerInWdDb: No lossless TC found on port Ethernet100
Add unit test to cover the new flow.

- How I did it
Before enabling PFCWD on a port, verify if PFC was previously enabled. If not, reply with an error to the user and as a warning in the log.
In the case where the command to enable PFCWD is done for all ports, the configuration will be applied for only those that has PCF enabled and for the rest the configuration will be skipped. In this case the output of the requested command will be only with a list of skipped ports.

- How to verify it
'pfcwd start EthernetX 600' where EthernetX is a port that has not configured PFC (usually admin state 'down' by default)
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
…dered (sonic-net#1937)

Signed-off-by: Neetha John <nejo@microsoft.com>

Fixes sonic-net/sonic-buildimage#9292

What I did
Pfcwd was not getting started after executing load_minigraph after the changes done in sonic-net#1508. This was because the PORT_QOS_MAP table is not yet present in config db (this gets populated only after the buffer templates are rendered) at the time we try to start pfcwd and hence the 'pfc_enable' field will always be empty and we skip writing PFC_WD table entries to config db.

How I did it
Delay pfcwd start until the buffer templates are rendered

How to verify it
Issue "config load_minigraph" with the changes and ensure that pfcwd is started on all active ports
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants