-
Bug
-
Resolution: Done
-
High
-
Guilin Release
According to read the docs there should be possibility to pre install root certificate for package validation by copping it directly to pod to /var/lib/jetty/cert in sdc-onboarding-be.
Currently aftre SDC deploy folder /dockerdata-nfs/{{ .Release.Name }}/sdc/onbaording/cert is not present
When user login to SDC onboarding pod he see
kubectl exec -it dev-sdc-onboarding-be-577b69b694-xxd22 -n onap bash Defaulting container name to sdc-onboarding-be. Use 'kubectl describe pod/dev-sdc-onboarding-be-577b69b694-xxd22 -n onap' to see all of the containers in this pod. jetty@dev-sdc-onboarding-be-577b69b694-xxd22:/var/lib/jetty$ ls -all total 64 drwxr-xr-x 1 jetty jetty 4096 Nov 2 17:04 . drwxr-xr-x 1 root root 4096 Sep 27 20:55 .. drwxr-xr-x 1 jetty jetty 4096 Nov 2 17:04 chef-solo drwxr-xr-x 3 jetty jetty 4096 Nov 2 17:04 config drwxr-xr-x 2 jetty jetty 4096 Nov 2 17:04 etc drwxr-xr-x 1 jetty jetty 4096 Sep 11 08:28 lib drwxr-xr-x 2 jetty jetty 4096 Nov 2 17:04 logs -rwxr-xr-x 1 jetty jetty 324 Nov 2 17:04 ready-probe.sh drwxr-xr-x 1 jetty jetty 4096 Sep 11 08:28 resources drwxr-xr-x 1 jetty jetty 4096 Nov 2 17:04 start.d -rwxrwx--- 1 jetty jetty 606 Sep 27 20:46 startup.sh drwxr-xr-x 2 jetty jetty 4096 Nov 2 17:04 temp -rw-r--r-- 1 jetty jetty 25 Nov 2 17:05 wait_logback.log drwxr-xr-x 1 jetty jetty 4096 Sep 27 20:56 webapps jetty@dev-sdc-onboarding-be-577b69b694-xxd22:/var/lib/jetty$
In robot test cases we prepared test case that was loading cert directly to sdc onboarding pod and validating VSP both in VNFSDK and SDC. Now we cannot validate secured packages in sdc onboarading.
It seems that folder cert is not mapped to folder in dockerdata-nfs at all.
