-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.14.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
1
-
Moderate
-
Yes
-
None
-
None
-
None
-
Done
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-44283. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-33682. The following is the description of the original issue:
—
Description of problem:
The cloud provider feature of NTO doesn't work as expected
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create a cloud-provider profile like as
apiVersion: tuned.openshift.io/v1
kind: Tuned
metadata:
name: provider-aws
namespace: openshift-cluster-node-tuning-operator
spec:
profile:
- data: |
[main]
summary=GCE Cloud provider-specific profile
# Your tuning for GCE Cloud provider goes here.
[sysctl]
vm.admin_reserve_kbytes=16386
name: provider-aws 2.
3.
Actual results:
the value of vm.admin_reserve_kbytes still using default value
Expected results:
the value of vm.admin_reserve_kbytes should change to 16386
Additional info:
- clones
-
OCPBUGS-44283 The setting of NTO cloud provider doesn't work
-
- Closed
-
- is blocked by
-
OCPBUGS-44283 The setting of NTO cloud provider doesn't work
-
- Closed
-
- links to
-
RHBA-2024:9620
OpenShift Container Platform 4.14.z bug fix update