Bug 1725089 - KubeMacPool causes many issues due to certificate handling
Summary: KubeMacPool causes many issues due to certificate handling
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Networking
Version: 2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.0
Assignee: Petr Horáček
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-28 11:57 UTC by Petr Horáček
Modified: 2019-07-24 20:16 UTC (History)
5 users (show)

Fixed In Version: hco-bundle-registry:v2.0.0-36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-24 20:16:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1850 0 None None None 2019-07-24 20:16:07 UTC

Description Petr Horáček 2019-06-28 11:57:56 UTC
Description of problem:
We recently observed multiple issues with KubeMacPool. It causes VMIs to fail while being created or migrated due to timeouts calling KubeMacPool admission webhook.

By removing KubeMacPool, we risk that two VMIs using secondary bridge network interfaces would end up with the same MAC address (although it is unlikely).

Since this bug is not limited to subset of VMI operations, but affects everyone (even when a VMI uses only the default network, it is in risk), we decided to drop KubeMacPool from CNV 2.0 in favor of stability.

This bug should be used to get acks and track PR disabling the feature.

Comment 1 Moran Goldboim 2019-07-01 12:39:20 UTC
acking on the request to remove mac-pool functionality out of the 2.0 release. mostly due to the fact that it didn't meet the done definition of done and pushed for 2.1

Comment 2 Meni Yakove 2019-07-08 12:42:23 UTC
hco-bundle-registry:v2.0.0-36

Comment 4 errata-xmlrpc 2019-07-24 20:16:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:1850


Note You need to log in before you can comment on or make changes to this bug.