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

OCPBUGS-17585 breaks IBM Managed OpenShift service

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • None
    • 4.13.z, 4.14.z
    • Node Tuning Operator
    • None

      Description of problem:

      The problem revolves around the explicit setting of the kubelet kubeconfig path here: https://github.com/openshift/cluster-node-tuning-operator/blob/78c64b23d6d0a5981322d0bbc47b400f3038860a/pkg/tuned/controller.go#L90-L91 (via this commit - https://github.com/openshift/cluster-node-tuning-operator/commit/0c4ce0a75983a7607856ec3d3f2d993e1b5e94a0#diff-ada285a2d7fbbe025a50a6a872690bf2a5140ec4d5de77095dd2df6855753388R90).

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

       

      How reproducible:

      100%

      Steps to Reproduce:

      1. Deploy an IBM Managed OpenShift Service cluster

      Actual results:

      1. All `tuned` pods in the `openshift-cluster-node-tuning-operator` namespace cannot start ('CrashloopBackoff')

      Expected results:

      `. 2. All `tuned` pods in the `openshift-cluster-node-tuning-operator` namespace start successfully.

      Additional info:

      IBM Managed OpenShift Service bootstrapping is expecting the kubeconfig path to be:  /etc/kubernetes/kubeconfig

            jmencak Jiri Mencak
            jeffbnowickirh Jeff Nowicki
            Liquan Cui Liquan Cui
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: