KubeVirt GenerateRandMAC

[chifu1234]

Bug Report

Describe the bug

When setting macAddress on the bridge of the VM, not every CNI implementation supports a deterministic MAC as they assign a MAC themself. The VM then gets the wrong MAC, and thus, no traffic is switched to the VM.

apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
  name: testerli-6cbbdfbcf7-bfrgv
  namespace: cluster-rb489cv8zn
spec:
  dataVolumeTemplates:
      labels:
    spec:
      domain:
        devices:
          interfaces:
          - bridge: {}
            macAddress: c2:4b:c4:9c:a5:f3
            name: default
...

Expected behavior

When creating Machine Deployment I can configure that kubermatic will not configure a RandomMac and the VM Object.

[kubermatic-bot]

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubermatic-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubermatic-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubermatic-bot]

@kubermatic-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[cnvergence]

/remove-lifecycle rotten