• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

openconfig / featureprofiles / 29729771581
9%
main: 9%

Build:
Build:
LAST BUILD BRANCH: arista-CNTR-2-fix-gnmi-cli-config
DEFAULT BRANCH: main
Ran 20 Jul 2026 03:28PM UTC
Jobs 1
Files 131
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

20 Jul 2026 07:02AM UTC coverage: 8.538% (+0.001%) from 8.537%
29729771581

Pull #5507

github

pjacakArista
CNTR-2: fix Arista container connectivity deviations

The CNTR-2 container connectivity flow fails on Arista EOS for several
independent reasons: containerz needs explicit EOS management API
configuration, the management namespace blocks the test container port,
the containerz endpoint uses a self-signed TLS certificate, gNOI/gNMI
connections can become stale after config-induced service restarts, and
the test expects FIB installation for a gRIBI decap entry that is only
needed for query coverage.

CNTR-2, containerz service configuration: configure the Arista gNMI and
gNOI/containerz management API using CLI-origin gNMI instead of the config
Append path. Save the config with retry, wait for the gNOI endpoint to
become reachable after the management service restart, and re-dial gNOI
before constructing the containerz client so the test does not reuse a
stale cached Ondatra connection.

CNTR-2, container port reachability: open TCP port 60061 directly in the
EOS management namespace. The namespace default policy drops the mapped
container port, and a direct ip6tables rule avoids relying on a per-VRF
control-plane ACL path that can be lost during the service restart window.

CNTR-2, containerz TLS: add a containerz_tls_insecure_skip_verify
deviation and use TLS with InsecureSkipVerify when dialing the test
container service on platforms that present a self-signed certificate.
Enable the deviation for Arista in the test metadata.

CNTR-2, DialGRPCWithPort binding: strip DUT per-RPC credentials for
arbitrary container service dials and default to insecure transport when
the device binding has no transport credentials configured. This avoids
gRPC credential conflicts while still allowing callers to pass explicit
transport credentials for TLS-backed container services.

CNTR-2, gRIBI setup: set Arista's default network instance to "default",
disable FIBACK, and expect the sample decap next-hop and next-hop-group
to be installed in RIB. The entries are only ... (continued)
Pull Request #5507: CNTR: fix Arista client setup and add Arista deviations

0 of 31 new or added lines in 3 files covered. (0.0%)

175 existing lines in 1 file now uncovered.

2305 of 26996 relevant lines covered (8.54%)

0.1 hits per line

Uncovered Changes

Lines Coverage ∆ File
23
31.66
-1.3% topologies/binding/binding.go
5
0.0
0.0% proto/metadata_go_proto/metadata.pb.go
3
0.0
0.0% internal/deviations/deviations.go

Coverage Regressions

Lines Coverage ∆ File
175
0.0
0.0% internal/security/acctz/acctz.go
Jobs
ID Job ID Ran Files Coverage
1 29729771581.1 20 Jul 2026 03:28PM UTC 131
8.54
GitHub Action Run
Source Files on build 29729771581
  • Tree
  • List 131
  • Changed 4
  • Source Changed 0
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Pull Request #5507
  • PR Base - main (#29748030407)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc