Uploaded image for project: 'Openshift sandboxed containers'
  1. Openshift sandboxed containers
  2. KATA-2976

OSC 1.6.0-41 is missing upstream cherry pick removing DISABLE_CLOUD_CONFIG from peer-pods-cm configmap

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • OSC 1.6.0
    • OSC 1.6.0
    • Operator
    • None
    • False
    • None
    • False
    • KATA-2590 - secure podvm configuration using metadata service
    • Kata Sprint #253
    • 0
    • 0

      Description

      Downstream code have this parameter in it and using DISABLE_CLOUD_CONFIG: "true" cause peer pods not been able to start

      Steps to reproduce

      1. install OSC 1.6.0-41 with peer pods enabled
      2. add DISABLE_CLOUD_CONFIG: "true" to peer-pod-cm configmap
      3. create the pod with kata-remote runtime

      Expected result

      Running

      Actual result

      Stack on initializing forever

      Env

      OCP 4.15.9 AWS

      Additional helpful info

      <logs, screenshot, doc links, etc.>

            bpradipt Pradipta Banerjee
            rhn-support-vvoronko Victor Voronkov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: