-
Notifications
You must be signed in to change notification settings - Fork 684
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
[PFCWD] Fix 'start' pfcwd command #1345
[PFCWD] Fix 'start' pfcwd command #1345
Conversation
Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>
retest this please |
retest this please |
"ports" and "detection-time" have been added as click arguments. This code hasn't changed. @click.option('--action', '-a', type=click.Choice(['drop', 'forward', 'alert'])) The right syntax would be: config pfcwd start --action drop --restoration-time 400 all 400 Looks like the documentation shows the same options that you used. Either the documentation should be changed, or the "port", "detection-time" should be changed to click options. |
you will have to update config/main.py |
@smaheshm can you please review the change? |
That's right. Not sure why pfcwd wasn't added as a module. Can you add a unit test that uses 'config pfcwd' CLI. |
@smaheshm calling the 'config' script to start pfcwd is failing on the unit-test environment, need to further investigate it. |
retest this please |
@smaheshm i agree that testing is always good to have. but in this case it is not the scopt. we are missing as a community various of test infra to add tests for bugs fixes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- [route_check.py] - update includes checks on subscriptions (sonic-net/sonic-utilities#1344) - Validations checks while adding a member to PortChannel and removing a member from a Portchannel (sonic-net/sonic-utilities#1328) - [show] Add subcommand to show midplane status for modular chassis (sonic-net/sonic-utilities#1267) - [pytest][qos][config] Added pytests for "config qos reload" commands" (sonic-net/sonic-utilities#1346) - Drop explict 3 seconds pause between two object updates/deletes. (sonic-net/sonic-utilities#1359) - [show]fix for show muxcable status by replacing "hostname" to "peer_switch" for deriving tor ipv4_address (sonic-net/sonic-utilities#1360) - [PFCWD] Fix 'start' pfcwd command (sonic-net/sonic-utilities#1345) Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>
- [route_check.py] - update includes checks on subscriptions (sonic-net/sonic-utilities#1344) - Validations checks while adding a member to PortChannel and removing a member from a Portchannel (sonic-net/sonic-utilities#1328) - [show] Add subcommand to show midplane status for modular chassis (sonic-net/sonic-utilities#1267) - [pytest][qos][config] Added pytests for "config qos reload" commands" (sonic-net/sonic-utilities#1346) - Drop explict 3 seconds pause between two object updates/deletes. (sonic-net/sonic-utilities#1359) - [show]fix for show muxcable status by replacing "hostname" to "peer_switch" for deriving tor ipv4_address (sonic-net/sonic-utilities#1360) - [PFCWD] Fix 'start' pfcwd command (sonic-net/sonic-utilities#1345) Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>
- What I did The 'config' method is getting arguments from the user CLI and build a proper command for the pfcwd script in a wrong way, causing this issue. - How I did it Fix the command structure to align with pfcwd.main script. - How to verify it Run "config pfcwd start --action drop ports all detection-time 400 --restoration-time 400" - Previous command output (if the output of a command-line utility has changed) config pfcwd start --action drop ports all detection-time 400 --restoration-time 400 Failed to run command, invalid options: ports detection-time
- What I did The 'config' method is getting arguments from the user CLI and build a proper command for the pfcwd script in a wrong way, causing this issue. - How I did it Fix the command structure to align with pfcwd.main script. - How to verify it Run "config pfcwd start --action drop ports all detection-time 400 --restoration-time 400" - Previous command output (if the output of a command-line utility has changed) config pfcwd start --action drop ports all detection-time 400 --restoration-time 400 Failed to run command, invalid options: ports detection-time
d324eae (HEAD -> 201911, origin/201911) [PFCWD] Fix 'start' pfcwd command (sonic-net#1345) 235c61c [ecnconfig] handle backend port names when extracting port I/F ID from the port name (sonic-net#1361) 7f5c3b4 Drop explict 3 seconds pause between two object updates/deletes. (sonic-net#1359) 12c8992 add vlan_intf_object only if there are ipv4 or ipv6 mappings (sonic-net#1377) 52ce2c3 Add subcommand description to interfaces counters (sonic-net#1373) Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>
- What I did
The 'config' method is getting arguments from the user CLI and build a proper command for the pfcwd script in a wrong way, causing this issue.
- How I did it
Fix the command structure to align with pfcwd.main script.
- How to verify it
Run "config pfcwd start --action drop ports all detection-time 400 --restoration-time 400"
- Previous command output (if the output of a command-line utility has changed)
config pfcwd start --action drop ports all detection-time 400 --restoration-time 400
Failed to run command, invalid options:
ports
detection-time
- New command output (if the output of a command-line utility has changed)
Command succeeded.