Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2074062

Summary: Node Tuning Operator(NTO) - Cloud provider profile rollback doesn't work well
Product: OpenShift Container Platform Reporter: liqcui
Component: Node Tuning OperatorAssignee: Jiří Mencák <jmencak>
Status: CLOSED ERRATA QA Contact: liqcui
Severity: medium Docs Contact:
Priority: medium    
Version: 4.11CC: dagray
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 11:05:57 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:

Description liqcui 2022-04-11 13:14:05 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Check the default value of vm.admin_reserve_kbytes 
oc rsh tuned_pod
sysctl vm.admin_reserve_kbytes

2. Create cloud provider profile provider-aws as below:
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. The new value of vm.admin_reserve_kbytes should be change to 16386
3. delete the tuned provider-aws

Actual results:
the value of vm.admin_reserve_kbytes still is 16386, no rollback

Expected results:
the value of vm.admin_reserve_kbytes should rollback to origin value.

Additional info:

Comment 1 Jiří Mencák 2022-04-11 13:45:11 UTC
Thank you for the report.  Reproduced on the latest nightly.

Comment 3 liqcui 2022-04-15 02:52:34 UTC
Verified Result:

[ocpadmin@ec2-18-217-45-133 nto]$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.nightly-2022-04-14-211051   True        False         47m     Cluster version is 4.11.0-0.nightly-2022-04-14-211051

cat cloud-aws.yaml
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

sh-4.4# sysctl vm.admin_reserve_kbytes
vm.admin_reserve_kbytes = 8192

[ocpadmin@ec2-18-217-45-133 nto]$ oc create -f cloud-aws.yaml
tuned.tuned.openshift.io/provider-aws created


sh-4.4# sysctl vm.admin_reserve_kbytes
vm.admin_reserve_kbytes = 16386


[ocpadmin@ec2-18-217-45-133 nto]$ oc delete -f cloud-aws.yaml
tuned.tuned.openshift.io "provider-aws" deleted

sh-4.4# sysctl vm.admin_reserve_kbytes
vm.admin_reserve_kbytes = 8192
sh-4.4#

Comment 6 errata-xmlrpc 2022-08-10 11:05:57 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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/RHSA-2022:5069