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

[RODOO] always setting activeDeadlineSeconds even user sets explicitly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.13
    • run-once-duration-override
    • None
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Bug Fix
    • Done

      Description of problem:

      If user sets activeDeadlineSeconds explicitly in pod.spec, RODOO always update this field even if user's value is less than the value specified in RODOO

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

       

      How reproducible:

      Set activeDeadlineSeconds in pod.yaml to something less than activeDeadlineSeconds in RODOO and see that it discards the value in pod.yaml

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

      It always sets the value specified in RODOO activeDeadlineSeconds

      Expected results:

      it should take the min value between pod.spec.ActiveDeadlineSeconds and RODOO activeDeadlineSeconds.

      Additional info:

       

              aguclu@redhat.com Arda Guclu
              aguclu@redhat.com Arda Guclu
              Rama Kasturi Narra Rama Kasturi Narra
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: