-
Notifications
You must be signed in to change notification settings - Fork 666
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
Feature table cli command update #1271
Conversation
Signed-off-by: Abhishek Dosi <[email protected]>
state and auto-restart fields Signed-off-by: Abhishek Dosi <[email protected]>
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.
LGTM. Can you also please update the Command Line Reference guide as part of this PR? I realized that the guide did not get updated once we changed the command from show/config container feature autorestart
to show/config feature autorestart
, and show/config feature state
were never added. See: https://github.com/Azure/sonic-utilities/blob/master/doc/Command-Reference.md#container-auto-restart.
Thus can you please do the following:
- Rename (and relocate alphabetically) the sections for
show/config container feature autorestart
toshow/config feature autorestart
and update the example output to display the "always_enabled" states - Add documentation for
show/config container feature state
commands
Signed-off-by: Abhishek Dosi <[email protected]>
Thanks @jleveque for pointing this out. I have updated the document accordingly. |
Signed-off-by: Abhishek Dosi <[email protected]>
Signed-off-by: Abhishek Dosi <[email protected]>
…d auto-restart fields. (#6000) Added new flag value 'always_enabled' for the state and auto-restart field of feature table init_cfg.json is updated to initialize state field of database/swss/syncd/teamd feature and auto-restart field of database feature as always_enabled Once the state/auto-restart value is initialized as "always_enabled" it is immutable and cannot be change via feature config commands. (config feature..) PR#sonic-net/sonic-utilities#1271 hostcfgd will not take any action if state field value is 'always_enabled' Since we have always_enabled field for auto-restart updated supervisor-proc-exit-listener not to have special check for database and always rely on value from Feature table.
…d auto-restart fields. (#6000) Added new flag value 'always_enabled' for the state and auto-restart field of feature table init_cfg.json is updated to initialize state field of database/swss/syncd/teamd feature and auto-restart field of database feature as always_enabled Once the state/auto-restart value is initialized as "always_enabled" it is immutable and cannot be change via feature config commands. (config feature..) PR#sonic-net/sonic-utilities#1271 hostcfgd will not take any action if state field value is 'always_enabled' Since we have always_enabled field for auto-restart updated supervisor-proc-exit-listener not to have special check for database and always rely on value from Feature table.
@daall Seems some issue with DVS test case for Policer. |
ack |
retest this please |
added new value "always_enabled" for the state and auto-restart field of Feature Table Once the field value is "always_enabled" it can be changes from config feature .. command Updated Command Reference Manual
…d auto-restart fields. (sonic-net#6000) Added new flag value 'always_enabled' for the state and auto-restart field of feature table init_cfg.json is updated to initialize state field of database/swss/syncd/teamd feature and auto-restart field of database feature as always_enabled Once the state/auto-restart value is initialized as "always_enabled" it is immutable and cannot be change via feature config commands. (config feature..) PR#sonic-net/sonic-utilities#1271 hostcfgd will not take any action if state field value is 'always_enabled' Since we have always_enabled field for auto-restart updated supervisor-proc-exit-listener not to have special check for database and always rely on value from Feature table.
[routeorch] Handle the empty "nexthop" field for backward compatibility (sonic-net#1263) [vnet] Set MTU for the VNET bridge RIF in BITMAP implementation (sonic-net#1271) [vnet] Verify if BITMAP route exists before creating new one to avoid dublication (sonic-net#1272)
49cd91d (HEAD -> 201911, origin/201911) Feature table cli command update (sonic-net#1271) 167d67a [201911] CRM show/config commands changes for multi-asic (sonic-net#1127) (sonic-net#1236) Signed-off-by: Abhishek Dosi <[email protected]>
…d auto-restart fields. (#6000) Added new flag value 'always_enabled' for the state and auto-restart field of feature table init_cfg.json is updated to initialize state field of database/swss/syncd/teamd feature and auto-restart field of database feature as always_enabled Once the state/auto-restart value is initialized as "always_enabled" it is immutable and cannot be change via feature config commands. (config feature..) PR#sonic-net/sonic-utilities#1271 hostcfgd will not take any action if state field value is 'always_enabled' Since we have always_enabled field for auto-restart updated supervisor-proc-exit-listener not to have special check for database and always rely on value from Feature table.
What I did:
added new value "always_enabled" for the state and auto-restart field of Feature Table
Once the field value is "always_enabled" it can-not be changed from config feature .. command
Updated Command Reference Manual
How I Verify:
Added the unit test case to change state/auto-restart field value of feature that has always_enabled and it should not update the field value.