Add IP interface loopback action related content to YANG models. #11012
Conversation
|
The following test is failing: |
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This reverts commit 5ac5a5e.
qiluo-msft
requested review from
prsunny,
dgsudharsan,
lolyu,
theasianpianist,
ganglyu and
isabelmsft
|
|
||
| leaf loopback_action { | ||
| description "Packet action when a packet ingress and gets routed on the same IP interface"; | ||
| type stypes:loopback_action; |
There was a problem hiding this comment.
shouldn't we specify the default action?
There was a problem hiding this comment.
@prsunny In general no. If we specify default action, this will be written to config_db. In case if the action is not implemented by other vendors there would be a SAI failure followed by orchagent crash.
So previously in yang subgroup we decided not to have default action for attributes that would be programmed into ASIC
|
The following test is failing: |
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Build mellanox failed in apt command execution, trying another rerun. |
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…ic-net#11012) *Add IP interface loopback action related content to the required YANG models.
Why I did it
Add IP interface loopback action related content to the required YANG models.
How I did it
Update the relevant YANG models.
How to verify it
New unittests were added.
Which release branch to backport (provide reason below if selected)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)