CNI base plugins version detection broken since CNI 1.4.0 (broken upstream)

[bfqrst]

Nomad version

Nomad v1.7.6
BuildDate 2024-03-12T07:27:36Z
Revision 594fedb

Operating system and Environment details

Ubuntu Jammy

Issue

Clients detail page in the Nomad UI shows 1.0.0 across the board for CNI plugins.

Reproduction steps

Check the respective UI page in the GUI of a v1.7.6 client.

Expected Result

Something like this on a v1.7.5 client tab:

Actual Result

Job file (if appropriate)

Nomad Server logs (if appropriate)

Nomad Client logs (if appropriate)

[tgross]

Hi @bfqrst I happen to have been working on something related to this recently, so this caught my eye right away. I checked this myself and with an older version of CNI plugins the fingerprint works fine, even with Nomad 1.7.6. But on the latest version, it looks like they're missing their version strings.

Ex. with 1.1.1

$ /opt/cni/bin/portmap --version
CNI portmap plugin v1.1.1

But with 1.4.1:

$ /opt/cni/bin/portmap --version
CNI portmap plugin version unknown
CNI protocol versions supported: 0.1.0, 0.2.0, 0.3.0, 0.3.1, 0.4.0, 1.0.0

So I think this is an upstream bug in the plugin builds? Can you check that on your cluster as well?

[tgross]

Ah, yeah I see this is reported upstream: containernetworking/plugins#1019

[tgross]

Fortunately we won't have to revert #15473 because we only required 0.4.0 and these will detect as 1.0.0 because of the way the version gets fingerprinted.

[bfqrst]

Ah, damn, could've checked myself upstream...

THX @tgross

[tgross]

Ok we'll leave this open until it's fixed upstream just so folks who come looking for it see it. Not much we can do from Nomad's side unfortunately, as the data just isn't in the --version output for us to get.

[bfqrst]

Understood, makes sense.

[tgross]

Upstream has re-released 1.4.1 (without a new version, see containernetworking/plugins#1038).

[bfqrst]

Confirming that v1.5.0 (the latest as of today) also shows fine in Nomad...

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.