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

Default ConfigMaps Piling up For Old Build Config

XMLWordPrintable

    • No
    • Pipeline Integrations #3248, Pipeline Integrations #3249, Pipeline Integrations #3250
    • 3
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Each build config creates three configmaps <NAME>-ca, <NAME>-global-ca, and <NAME>-sys-config which generally stays in the namespace even after build completes. 
      
      Due to old configmaps in the namespace, resource quota prevents creating new configmaps and end up failing the build.
      
      Each time user needs to delete the old configmaps and then build gets succeeded.

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

       

      How reproducible:

      Every build config creates the configmaps by default

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

      Old configmaps stays in the namespace.

      Expected results:

      Clean the old configmaps once build process completes.

      Additional info:

       

            rh-ee-sabiswas Sayan Biswas
            rhn-support-ssardar Sameer Sardar
            Jitendar Singh Jitendar Singh
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: