ci: update OFED version to doca3.3.3-26.01-2.0.0.0.615-0

[nvidia-ci-cd]

Created by an internal DOCA CI job.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[greptile-apps]

Confidence Score: 3/5

[Medium risk] Updates OFED driver version in example configurations.

The PR is not safe to merge until the new tag is accepted by admission and the driver-check target can locate its release manifest.

Findings

1.  New driver tag fails admission ▶
2.  Driver check requests wrong manifest ▶

Summary

The PR changes the DOCA driver version in seven example policies and the normal and STIG/FIPS release-image entries.

• The example policies’ new tag is rejected by OFED admission validation.
• The new tag format also breaks the driver-check target’s release-manifest lookup.

_{Reviews (1) · Last reviewed commit: "ci: update OFED version to doca3.3.3-26...."}

[greptile-apps]

New driver tag fails admission Applying this example, or any of the other six updated example policies, is rejected with “invalid OFED version.” The validator accepts either a four-part dotted driver version or a six-or-more-digit build number after 26.01; the new tag contains the five-part value 2.0.0.0.615, so none of the updated examples can be applied.

Knowledge Base Used: NIC cluster and node policy resources

[greptile-apps]

Driver check requests wrong manifest With this new tag, make check-doca-drivers no longer extracts 26.01 as the release manifest name. Its version extraction strips only DOCA prefixes ending in .0, so it instead requests doca3.3.3.yaml and cannot perform the driver-tag check.