Adding RT-3.53: Static route based GUE Encapsulation to IPv4 tunnel
Readme Location: https://github.com/openconfig/featureprofiles/blob/main/feature/static/otg_tests/next_hop_encap_udp/README.md
The log is attached here: https://partnerissuetracker.corp.google.com/issues/415458482
Pull Request Functional Test Report for #4409 / 898f3ffa75f3775a084a5b774546811bc0c91ff3
Virtual Devices
| Device | Test | Test Documentation | Job | Raw Log |
|---|---|---|---|---|
| Arista cEOS | RT-3.53: Static route based GUE Encapsulation to IPv4 tunnel |
|||
| Cisco 8000E | RT-3.53: Static route based GUE Encapsulation to IPv4 tunnel |
|||
| Cisco XRd | RT-3.53: Static route based GUE Encapsulation to IPv4 tunnel |
|||
| Juniper ncPTX | RT-3.53: Static route based GUE Encapsulation to IPv4 tunnel |
|||
| Nokia SR Linux | RT-3.53: Static route based GUE Encapsulation to IPv4 tunnel |
|||
| Openconfig Lemming | RT-3.53: Static route based GUE Encapsulation to IPv4 tunnel |
Hardware Devices
| Device | Test | Test Documentation | Raw Log |
|---|---|---|---|
| Arista 7808 | RT-3.53: Static route based GUE Encapsulation to IPv4 tunnel |
||
| Cisco 8808 | RT-3.53: Static route based GUE Encapsulation to IPv4 tunnel |
||
| Juniper PTX10008 | RT-3.53: Static route based GUE Encapsulation to IPv4 tunnel |
||
| Nokia 7250 IXR-10e | RT-3.53: Static route based GUE Encapsulation to IPv4 tunnel |
Pull Request Test Coverage Report for Build 19930102360
Details
- 0 of 97 (0.0%) changed or added relevant lines in 5 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage decreased (-0.04%) to 10.077%
| Changes Missing Coverage | Covered Lines | Changed/Added Lines | % |
|---|---|---|---|
| internal/deviations/deviations.go | 0 | 3 | 0.0% |
| internal/cfgplugins/bgp.go | 0 | 4 | 0.0% |
| proto/metadata_go_proto/metadata.pb.go | 0 | 5 | 0.0% |
| internal/cfgplugins/staticnexthop.go | 0 | 37 | 0.0% |
| internal/cfgplugins/staticroute.go | 0 | 48 | 0.0% |
| <!-- | Total: | 0 | 97 |
| Totals | |
|---|---|
| Change from base Build 19923363524: | -0.04% |
| Covered Lines: | 2227 |
| Relevant Lines: | 22099 |
💛 - Coveralls
please rebase the folder to google3/third_party/openconfig/featureprofiles/feature/static/otg_tests/next_hop_encap_udp/
@ASHNA-AGGARWAL-KEYSIGHT please resolve all conversations post fixing them
After changes, please provide test run logs
After changes, please provide test run logs
New logs(RT3.53-hwlogNew): https://partnerissuetracker.corp.google.com/issues/415458482
Pre-merge Action: @ram-mac , kindly execute this test within our environment before merging. We can proceed with the merge upon successful test completion
/fptest all
/fptest physical
This test fails to apply the gnmi.CLI configuration on the device. Below is the error for the same. So, traffic-policy tcam configuration needs to be applied to the test for the test to work. Attached the logs for reference. https://partnerissuetracker.corp.google.com/issues/415458482 comment#123
[third_party/openconfig/featureprofiles/internal/helpers/helpers.go:136](: gnmiClient.Set() with unexpected error: rpc error: code = InvalidArgument desc = error on request {
update: {
path: {
origin: "cli"
}
val: {
ascii_val: "\n\t\t\t\ttraffic-policies\n\t\t\t\ttraffic-policy GUE-Policy\n \t\t\tmatch rule1 ipv4\n \t\tactions\n \tredirect next-hop group GUE-NHG"
}
}
}: failed to apply: Failed to commit traffic-policy : Port traffic-policy not supported in TCAM profile: ERROR: session commit failed, no checkpoint to rollback to: CLI command 9 of 9 'configure session session828200000845784 commit' failed: could not run command
I have attached the TCAM configuration required for the ngPR and this should be added to the test using below function. https://partnerissuetracker.corp.google.com/issues/415458482 comment#121 Will test with this TCAM configuration and update the results here.
func configureHardwareInit(t *testing.T, dut *ondatra.DUTDevice) {
hardwareInitCfg := cfgplugins.NewDUTHardwareInit(t, dut, cfgplugins.FeatureTrafficPolicy)
if hardwareInitCfg == "" {
return
}
cfgplugins.PushDUTHardwareInitConfig(t, dut, hardwareInitCfg)
}
func mustConfigureDUT(t *testing.T, dut *ondatra.DUTDevice) {
t.Helper()
// Configure hardware init config which includes the TCAM configuration.
configureHardwareInit(t, dut)
@ASHNA-AGGARWAL-KEYSIGHT - I tried running the test with the TCAM configuration and the test is failing with the below error. Can you check on your setup if you are able to run this test without any issues? Have attached the logs to the bug for reference. https://partnerissuetracker.corp.google.com/issues/415458482 comment#124
[third_party/openconfig/featureprofiles/internal/helpers/helpers.go:136] gnmiClient.Set() with unexpected error: rpc error: code = InvalidArgument desc = error on request {
update: {
path: {
origin: "cli"
}
val: {
ascii_val: "\n\t\t\t\ttraffic-policies\n\t\t\t\ttraffic-policy GUE-Policy\n \t\t\tmatch rule1 ipv4\n \t\tactions\n \tredirect next-hop group GUE-NHG"
}
}
}: failed to apply: Failed to commit traffic-policy : timeout: ERROR: session commit failed, no checkpoint to rollback to: CLI command 9 of 9 'configure session session831620101311530 commit' failed: could not run command
@ASHNA-AGGARWAL-KEYSIGHT - I tried running the test with the TCAM configuration and the test is failing with the below error. Can you check on your setup if you are able to run this test without any issues? Have attached the logs to the bug for reference. https://partnerissuetracker.corp.google.com/issues/415458482 comment#124
[third_party/openconfig/featureprofiles/internal/helpers/helpers.go:136] gnmiClient.Set() with unexpected error: rpc error: code = InvalidArgument desc = error on request { update: { path: { origin: "cli" } val: { ascii_val: "\n\t\t\t\ttraffic-policies\n\t\t\t\ttraffic-policy GUE-Policy\n \t\t\tmatch rule1 ipv4\n \t\tactions\n \tredirect next-hop group GUE-NHG" } } }: failed to apply: Failed to commit traffic-policy : timeout: ERROR: session commit failed, no checkpoint to rollback to: CLI command 9 of 9 'configure session session831620101311530 commit' failed: could not run command
Added the TCAM changes. Pass logs attached(RT3.53-TcamLogs) - https://partnerissuetracker.corp.google.com/issues/415458482
@ASHNA-AGGARWAL-KEYSIGHT - I ran the test with the latest changes and at least the initial issue of failing to apply config is gone. However the test is failing to capture with the below error for all the subtests. Will upload the test logs to https://partnerissuetracker.corp.google.com/issues/415458482 - comment#133. Take a look and suggest any fix for this issue.
third_party/openconfig/featureprofiles/feature/static/otg_tests/next_hop_encap_udp/static_encap_gue_ipv4_test.go:715: SetControlState(t) on [ixia04-den86.corp.google.com](http://ixia04-den86.corp.google.com/)(Session 1): {
"code": 13,
"errors": [
"error after request {\nchunk_size: 4000000\ndatum: \"\\x08\\x01\\x12\\x06\\x08\\x02\\x1a\\x02\\x10\\x01\"\n}: {\n \"code\": 13,\n \"kind\": \"internal\",\n \"errors\": [\n \"Error occurred while capturing start: [Could not start capture on selected port(s) because this would exceed the maximum number of active capture ports per card. Currently active capture ports are: { For card 2 : 3, 6 }]\"\n ]\n}"
]
}
@ASHNA-AGGARWAL-KEYSIGHT - I ran the test with the latest changes and at least the initial issue of failing to apply config is gone. However the test is failing to capture with the below error for all the subtests. Will upload the test logs to https://partnerissuetracker.corp.google.com/issues/415458482 - comment#133. Take a look and suggest any fix for this issue.
third_party/openconfig/featureprofiles/feature/static/otg_tests/next_hop_encap_udp/static_encap_gue_ipv4_test.go:715: SetControlState(t) on [ixia04-den86.corp.google.com](http://ixia04-den86.corp.google.com/)(Session 1): { "code": 13, "errors": [ "error after request {\nchunk_size: 4000000\ndatum: \"\\x08\\x01\\x12\\x06\\x08\\x02\\x1a\\x02\\x10\\x01\"\n}: {\n \"code\": 13,\n \"kind\": \"internal\",\n \"errors\": [\n \"Error occurred while capturing start: [Could not start capture on selected port(s) because this would exceed the maximum number of active capture ports per card. Currently active capture ports are: { For card 2 : 3, 6 }]\"\n ]\n}" ] }
@ram-mac, Could you try executing on another card as communicated?