Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-544

Long docker pulls cause timeouts on pod startup - make crashLoopRestart policy configurable/extended

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Casablanca Release
    • Component/s: None
    • Labels:
    • Sprint:
      R3 Sprint 1

      Description

      See issues with OOM-537 related to the new SDNC-163

      17:41:54 5 pending > 0 at the 88th 15 sec interval
      17:42:10 onap-aaf              aaf-1993711932-934l1                          0/1       Running    0          25m
      17:42:10 onap-sdnc             sdnc-0                                        0/2       Init:0/1   2          28m
      17:42:10 onap-sdnc             sdnc-dbhost-0                                 0/2       Pending    0          28m
      17:42:10 onap-sdnc             sdnc-dgbuilder-4267203648-kdcrf               0/1       Init:0/1   2          28m
      17:42:10 onap-sdnc             sdnc-portal-2558294154-j6jx7                  0/1       Init:0/1   2          28m
      

      workaround is to restart SDNC on a clean machine
      A 2nd createAll will not experience the issue because the docker images were already pulled

      Pending (michael) get logs from a clean deployment and add here

        Attachments

          Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              michaelobrien Michael O'Brien
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: