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

ONAP health check fails and not recovered after a k8s cluster node failure

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Duplicate
    • Affects Version/s: Casablanca Release
    • Component/s: None
    • Labels:
    • Environment:

      OOM on SB05. The failing nod is oom-k8s-10.

    • Sprint:
      Casablanca-3.0.1 (12/01-01/29)

      Description

      After running ONAP for 6 days, a k8s cluster node failed. Then health check failed for a few ONAP components and no recovery is seen after a few hours. 

      Did a hard reboot of the node from Openstack Horizon, afterwards the node is still not shown in command 'kubectl -n onap get node'. 

      As the first step, please provide a manual recovery procedure, so we can downgrade the bug

        Attachments

          Issue Links

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

            Activity

              People

              Assignee:
              melliott Mike Elliott
              Reporter:
              xuyang11 Yang Xu
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: