The ONAP Master deployment (using OOM) on our daily CI/CD chain are FAIL since week 4 due to the pod   onap-sdc-sdc-fe

After a fresh installation , the pod is not fully up

onap-sdc-sdc-fe-6cbdc66dcd-jppqs 1/2 Running 60 3h

As a consequence, SDC healthcheck test is FAIL.

------------------------------------------------------------------------------
Basic SDC Health Check | FAIL |
Test timeout 10 seconds exceeded.
------------------------------------------------------------------------------

In the logs (full log attached) we can read

kubectl logs onap-sdc-sdc-fe-6cbdc66dcd-jppqs -n onap -c sdc-fe

......

[2019-02-01T08:12:17+00:00] INFO: Storing updated cookbooks/sdc-catalog-fe/templates/default/http-ini.erb in the cache.

• sdc-catalog-fe (0.0.0)
  Installing Cookbook Gems:
  Compiling Cookbooks...

================================================================================
R*ecipe Compile Error in /root/chef-solo/cache/cookbooks/sdc-catalog-fe/recipes/FE_2_setup_configuration.rb*
================================================================================

NoMethodError
-------------
undefined method `[]' for nil:NilClass

...

Chef Client failed. 0 resources updated in 01 seconds
[2019-02-01T08:12:17+00:00] FATAL: Stacktrace dumped to /root/chef-solo/cache/chef-stacktrace.out

[2019-02-01T08:12:17+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2019-02-01T08:12:17+00:00] ERROR: undefined method `[]' for nil:NilClass
[2019-02-01T08:12:17+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

Impossible to retrieve the /root/chef-solo/cache/chef-stacktrace.out

error: unable to upgrade connection: container not found ("sdc-fe")