Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-42219

[VM Latency Checkup] Setup does not have a dedicated timeout

XMLWordPrintable

    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • ---
    • ---
    • Low
    • No

      Description of problem:

      Currently, the setup phase of the VM latency checkup is not bounded by a dedicated timeout - only by the general context with timeout for the whole checkup.Add a context with timeout derived from the general context - similar to what is done in the DPDK and real-time checkups.

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

      4.16

      How reproducible:

      100%

      Steps to Reproduce:

      1. In the user-supplied ConfigMap:
       - Define spec.timeout: 15m
       - Define non-existant nodes for spec.param.sourceNode and spec.param.targetNode
      
      2. Run the checkup.
      4. The checkup will wait for the full timeout because the VMIs will not be scheduled.

      Actual results:

      The checkup will fail because the overall timeout had expired

      Expected results:

      The checkup should fail because the setup timeout had expired

      Additional info:

      https://github.com/kiagnose/kiagnose/issues/258

            omisan@redhat.com Orel Misan
            omisan@redhat.com Orel Misan
            Nir Rozen Nir Rozen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: