Bug 2058197 - nfd-worker: drop 'custom-' prefix from matchFeatures custom rules
Summary: nfd-worker: drop 'custom-' prefix from matchFeatures custom rules
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node Feature Discovery Operator
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.10.0
Assignee: Carlos Eduardo Arango Gutierrez
QA Contact: Lena Horsley
URL:
Whiteboard:
Depends On: 2057569
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-24 13:42 UTC by OpenShift BugZilla Robot
Modified: 2022-03-10 15:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 15:56:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift node-feature-discovery pull 80 0 None open [release-4.10] Bug 2058197: nfd-worker: drop 'custom-' prefix from matchFeatures custom rules 2022-02-24 13:42:36 UTC
Red Hat Product Errata RHBA-2022:0057 0 None None None 2022-03-10 15:56:53 UTC

Description OpenShift BugZilla Robot 2022-02-24 13:42:24 UTC 
+++ This bug was initially created as a clone of Bug #2057569 +++

Do not prefix label names from the new matchFeatures/matchAny custom
rules with "custom-". We want to have the same result (set of labels)
from a rule independent of whether it has been specified in worker
config or in a NodeFeatureRule CRs. Legacy matchOn rules (not available
in NodeFeatureRule CRs) are intact, i.e. still prefixed, in order to
retain backwards compatibility.
Comment 5 errata-xmlrpc 2022-03-10 15:56:50 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 (OpenShift Container Platform 4.10.3 extras update), 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/RHBA-2022:0057
Note You need to log in before you can comment on or make changes to this bug.