Uploaded image for project: 'Holmes'
  1. Holmes
  2. HOLMES-429

HOLMES rules and engine fail to start on dualstack after migration to Helm

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: High High
    • Honolulu Release
    • Honolulu Release
    • None
    • Holmes Sprint 54

      Hello,

      After migration of HOLMES from cloudify to helm it fails to start on dualstack environment (it means that each pod has 2 IPs. One IPv4 and one IPv6).

      As you can see here: https://logs.onap.org/onap-integration/daily/onap_daily_nokia_dualstack_master/ci-ds-2021-04-03-01-21-37/

      Since this moment the Holmes health check fails as the pods are in the CrashLoopBackOff  state.

      dev-holmes-engine-mgmt-787d9b66c4-5rnvw 0/1 CrashLoopBackOff 
      dev-holmes-rule-mgmt-5b497fdb8-rbkrl 0/1 CrashLoopBackOff

      The health check test case was updated at 3rd of April that is why we didn't see this error before and the commit od from 27th of March

       

      The log shows the same error for both pods:

      /opt/onap/bin/run.sh: 60: export: 10.242.76.172: bad variable name

      Of course both of them have different IPs but the exception is the same.

      If you need any logs/ traces etc just let me know.

      Thank you!

            guangrongfu guangrongfu
            grzegorz-lis grzegorz-lis
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: