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

The setting of NTO cloud provider doesn't work

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • None
    • 4.14.z
    • Node Tuning Operator
    • None
    • Moderate
    • Yes
    • 1
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • Done

      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:

          

              jmencak Jiri Mencak
              openshift-crt-jira-prow OpenShift Prow Bot
              Liquan Cui Liquan Cui
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: