Bug 1685549 - Label case mismatch between kubevirt and NFD cpu model plugin
Summary: Label case mismatch between kubevirt and NFD cpu model plugin
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 1.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.0
Assignee: Karel Šimon
QA Contact: guy chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-05 13:14 UTC by Martin Sivák
Modified: 2019-07-24 20:16 UTC (History)
6 users (show)

Fixed In Version: 2.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-24 20:15:51 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:15:59 UTC

Description Martin Sivák 2019-03-05 13:14:35 UTC 
Description of problem:

When CPUNodeDiscovery feature gate is enabled, kubevirt creates node selector labels with first capital letter of cpu model, e.g. feature.node.kubernetes.io/cpu-model-Conroe.

But kubevirt-cpu-model-nfd-plugin lowers first letter of cpu model, e.g. feature.node.kubernetes.io/cpu-model-conroe.

Kubernetes is case sensitive when selecting node labels => VM is unschedulable, because it cannot find correct label.

Version-Release number of selected component (if applicable):

CNV/kubevirt 1.4
Comment 1 Martin Sivák 2019-03-26 13:18:20 UTC 
Fixed in https://github.com/ksimon1/kubevirt-cpu-nfd-plugin/commit/9c5153c4959bedcce106b79498a611e4943cac01
Comment 3 guy chen 2019-06-20 13:53:09 UTC 
Was tested on build 29 and verified as fixed.
Comment 5 errata-xmlrpc 2019-07-24 20:15:51 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.