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

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Medium Medium
    • Casablanca Maintenance Release
    • Casablanca Release
    • None

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

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

      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

            melliott melliott
            xuyang11 xuyang11
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: