Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test failures with new multus 4.1.1 (thick/thin) #124

Open
oshoval opened this issue Sep 26, 2024 · 2 comments
Open

Test failures with new multus 4.1.1 (thick/thin) #124

oshoval opened this issue Sep 26, 2024 · 2 comments
Labels

Comments

@oshoval
Copy link
Contributor

oshoval commented Sep 26, 2024

What happened:
Instead deploying CNAO's multus, deploy multus 4.1.1 and run tests
one test always fail

macvtap-cni
/root/go/src/github.com/macvtap-cni/tests/e2e/macvtap_test.go:66
  macvtap resource creation
  /root/go/src/github.com/macvtap-cni/tests/e2e/macvtap_test.go:114
    WHEN a macvtap interface is configured as a secondary interface
    /root/go/src/github.com/macvtap-cni/tests/e2e/macvtap_test.go:116
      WHEN a pod requests aforementioned macvtap resource
      /root/go/src/github.com/macvtap-cni/tests/e2e/macvtap_test.go:127
        SHOULD successfully get a second interface, of macvtap type, with configured MAC address [It]
        /root/go/src/github.com/macvtap-cni/tests/e2e/macvtap_test.go:168

        Expected
            <[]tests_test.reportedNetwork | len:1, cap:4>: [
                {
                    Name: "default/macvtap0",
                    Interface: "net1",
                    Mac: "a6:62:96:1b:ad:e3",
                    Dns: {},
                },
            ]
        to have length 2

        /root/go/src/github.com/macvtap-cni/tests/e2e/macvtap_test.go:184

What you expected to happen:
Should pass

How to reproduce it (as minimally and precisely as possible):
as seen above

Additional context:

Environment:

  • KubeVirt version (use virtctl version): N/A
  • Kubernetes version (use kubectl version): N/A
  • VM or VMI specifications: N/A
  • Cloud provider or hardware configuration: N/A
  • OS (e.g. from /etc/os-release): N/A
  • Kernel (e.g. uname -a): N/A
  • Install tools: N/A
  • Others: N/A
@oshoval oshoval changed the title Test falilures with new multus 4.1.1 (thick/thin) Test failures with new multus 4.1.1 (thick/thin) Sep 26, 2024
@oshoval
Copy link
Contributor Author

oshoval commented Oct 1, 2024

should be fixed once new multus is released (kubevirtci + cnao bump is required first, since the multus that is deployed is via CNAO iirc)
k8snetworkplumbingwg/network-attachment-definition-client#72
k8snetworkplumbingwg/multus-cni#1341
Thanks

@oshoval
Copy link
Contributor Author

oshoval commented Oct 1, 2024

@maiqueb
We would need please a new multus release that includes this fix
k8snetworkplumbingwg/multus-cni#1341
I guess Doug will create it soon, and just need to wait right ?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant