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

Restart of worker node with peer pods running leave podvms running forever on AWS cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Medium Medium
    • None
    • OSC 1.6.0
    • podvm
    • None
    • False
    • None
    • False
    • 0
    • 0

      Description

      After peer pods been launched on a worker and this worker been rebooted from terminal, OSC doesn't cleanup the resources and after the reboot starts a new ones

      Steps to reproduce

      <What actions did you take to hit the bug?>
      1. Deploy OSC 1.6.0-41 on AWS OCP 4.15.9 cluster with peer pods enabled
      2. Run a couple of peer pods on a worker node
      3. Reboot this worker node from the terminal

      Expected result

      podvms been terminated

      Actual result

      podvms are running forever

      Impact

      Customer cloud billingĀ 

      Env

      OCP 4.15.9 on AWS + OSC 1.6.0-41

      Additional helpful info

      <logs, screenshot, doc links, etc.>

            ssheribe@redhat.com Snir sheriber
            rhn-support-vvoronko Victor Voronkov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: