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

MOSB status is not updated properly even when buildpods are not present

XMLWordPrintable

    • None
    • 3
    • MCO Sprint 259, MCO Sprint 260, MCO Sprint 261, MCO Sprint 262
    • 4
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

      The MOSB status is been showing failed and buildpods are terminated after a while not been in error state.This was observed while verifying OCPBUGS-36172 where after MC was configured to trigger MOSB. And for first build is showing false for all status

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

          

      How reproducible:

          

      Steps to Reproduce:

      1.Enable OCB functionality
      2.Build the first run for MOSB
      3.Fix the secrets
      4.Configured MC to trigger the second build for MOSB
      5.MOSB is failed and buildpod is terminated after a while and for first build the MOSB is false for all status.

      NAME                                                            PREPARED   BUILDING   SUCCEEDED   INTERRUPTED   FAILED
      infra-rendered-infra-410552d428fbf83a812bb70269c8f7ef-builder   False      False      False       False         True
      infra-rendered-infra-d6110cd608bfcdb3f0bac57554204e60-builder   False      False      False       False         False
      

       

      Actual results:

          MOSB should be succeeded  

      Expected results:

          

      Additional info:

          

              rh-ee-rsaini Rishabh Saini
              rh-ee-ptalgulk Prachiti Talgulkar
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: