Bug 1881422
Summary: | NTO does not create machine config for the master machine config pool | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Artyom <alukiano> |
Component: | Node Tuning Operator | Assignee: | Jiří Mencák <jmencak> |
Status: | CLOSED ERRATA | QA Contact: | Simon <skordas> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.6 | CC: | alukiano, cswanson, dshchedr, fiezzi, pibanezr, sejug |
Target Milestone: | --- | ||
Target Release: | 4.6.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-10-27 16:44:29 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1882005 |
Description
Artyom
2020-09-22 11:42:49 UTC
You seem to be using openshift-node-performance-hp-performanceprofile with priority 30. In all likelihood, there's default Tuned profile "" with the same priority (30). See: https://github.com/openshift/cluster-node-tuning-operator/blob/8b9aeeda1b13f2c6130a54d89be003fd18ee828f/assets/tuned/manifests/default-cr-tuned.yaml#L72 In this case, if both profiles match a node, the profile selection is random. I'd recommend always create profiles with unique priorities to avoid issues like these. I'll see how can I improve things from NTO side. The easiest and quickest to implement seems issuing an operator warning to the user. Verified on 4.6.0-0.nightly-2020-10-02-043144 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.6 GA Images), 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-2020:4196 |