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

Pods with topolvm PVC are taking a long time to start after machine reboot

    XMLWordPrintable

Details

    • No
    • uShift Sprint 232, uShift Sprint 233, uShift Sprint 234
    • 3
    • Rejected
    • False
    • Hide

      None

      Show
      None

    Description

      This bug is extracted from https://issues.redhat.com/browse/OCPBUGS-6861

       

      Description of problem:

      After rebooting machine with MicroShift, Pods using topolvm PVC are taking really long time to come back online (about 2-3 minutes longer than "system" microshift Pods)

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

      ABB Edgenius OS 0.3.1 based on Microshift 4.12 RC3 and RHEL 8.7

      How reproducible:

      100%

      Steps to Reproduce:

      1. Deploy a Pod with PVC using topolvm StorageClass
2. Reboot the machine
3. After rebooting observe the Pods, e.g. watch kubectl get pods -A

      Actual results:

      Pod with PVC is running/ready after ~4 minutes from boot

      Expected results:

      Pod with PVC is running/ready shortly after topolvm controller and node starts.
What shortly means - something more reasonable than 2-3 minutes, let say below 30 seconds? TBD

      Additional info:

       

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-8021 Pods with topolvm PVC are taking a long time to start after machine reboot

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-8021 Pods with topolvm PVC are taking a long time to start after machine reboot

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          split from

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-6861 Some pods not coming up after rebooting

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-10256 Some pods not coming up after rebooting

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              pmatusza@redhat.com Patryk Matuszak
              pmatusza@redhat.com Patryk Matuszak
              John George John George
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: