Bug 1908743

Summary:	KubeMacPool component must be enabled in infrastructure namespace
Product:	OpenShift Container Platform	Reporter:	Nir Argaman <nargaman>
Component:	Cloud Compute	Assignee:	Nir Argaman <nargaman>
Cloud Compute sub component:	KubeVirt Provider	QA Contact:	Chen Yosef <cyosef>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	high
Priority:	high	CC:	aos-bugs, danken, phoracek
Version:	4.7	Flags:	cyosef: needinfo+ phoracek: needinfo-
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-10 08:26:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nir Argaman 2020-12-17 13:38:24 UTC

Description of problem:

Enable the KubeMacPool component for the namespace, virtual machine NICs in that namespace are allocated MAC addresses from a MAC address pool. This ensures that  virtual machine instances created from that virtual machine retain the assigned MAC address across reboots.
In order to do that, add the KubeMacPool label to the namespace, run: oc label namespace <namespace> mutatevirtualmachines.kubemacpool.io=allocate
For more information go to https://docs.openshift.com/container-platform/4.6/virt/virtual_machines/vm_networking/virt-using-mac-address-pool-for-vms.html

Comment 1 Chen Yosef 2020-12-20 15:44:46 UTC

@danken @phoracek What are the plans to make this the default behavior of KubeVirt / OPenshfit Virtualization ? Retaining the mac address after VM restart seems like a basic feature of any virtualization platform.

Comment 4 Petr Horáček 2021-01-04 10:29:37 UTC

Nir, could you please help me understand what changed to move this to verified? The title of the PR "Add validation that the KubeMacPool component is enabled for the namespace" suggests that KMP is now a hard requirement for CNV. Is that the case?

Comment 5 Chen Yosef 2021-01-04 10:51:25 UTC

@phoracek KMP is now a hard requirement for the namespace where the tenant cluster is installed in. The installer will now verify that the namespace where the user wants to install the tenant cluster in has the appropriate KMP label.