Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-38796

The sysctl value will revert after reboot node twice when create profile with tuned.openshift.io/deferred: "update" annotation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.18
    • Node Tuning Operator
    • None
    • Important
    • None
    • Proposed
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Deleting a profile with annotation tuned.openshift.io/deferred: update, then apply the same profile again, the profile will immediately apply.  Then edit the profile and change to a new value, reboot first time, the new value applied, then reboot again, it will restore to default value.    

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

          

      How reproducible:

          

      Steps to Reproduce:

          1. Create a new OCP using latest 4.18 nightly version
          2. Creating a profile with annotation tuned.openshift.io/deferred: update
          3. The profile will immediately apply.  
          4. Then edit the profile and change to a new value
          5. reboot node twice, the sysctl value will restore to default value.

      Actual results:

          After rebooting node twice, the specified sysctl value will revert to default value

      Expected results:

          the specified sysctl value should keep the value as setting in tuned profile
           More detailed step, please check the second issue in the doc https://docs.google.com/document/d/1h-7AIyqf7sHa5Et2XF7a-RuuejwVkrjhiFFzqZnNfvg/edit

      Additional info:

          

              msivak@redhat.com Martin Sivak
              rhn-support-liqcui Liquan Cui
              Liquan Cui Liquan Cui
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: