-
Bug
-
Resolution: Cannot Reproduce
-
Medium
-
Frankfurt Release
-
None
this morning, on the daily frankfurt, the SDNC healthcheck test was failed leading to failure in most of the other tests (SDNC is part of the core components and reused in almost all the use cases)
The healthcheck error is
Basic SDNC Health Check | FAIL |
Resolving variable '${resp.json()['output']['response-code']}' failed: JSONDecodeError: Expecting value: line 1 column 1 (char 0)
-
When I look at the log
kubectl logs onap-sdnc-0 -n onap -c sdnc
Settings:
ENABLE_ODL_CLUSTER=true
SDNC_REPLICAS=1
SDNRWT=false
AAF_ENABLED=true
Installing SDN-C keyStore
Replace boot feature odl-netconf-connector-all, with:
Installing Opendaylight cluster features
Replace boot feature odl-netconf-topology with: odl-netconf-clustered-topology
Replace boot feature odl-mdsal-all with: odl-mdsal-all,odl-mdsal-clustering
Add boot feature: odl-jolokia
Update cluster information statically
Get current Hostname onap-sdnc-0
This is a local cluster
################################################
## Configure Cluster ##
################################################
NOTE: Cluster configuration files not found. Copying from
/opt/opendaylight/current/system/org/opendaylight/controller/sal-clustering-config/1.9.1
Configuring unique name in akka.conf
Configuring hostname in akka.conf
Configuring data and rpc seed nodes in akka.conf
modules = [
,
,
]
Configuring replication type in module-shards.conf
################################################
## NOTE: Manually restart controller to ##
## apply configuration. ##
################################################
cp: can't stat '/opt/opendaylight/current/certs/': No such file or directory*
/opt/opendaylight/bin/karaf: /opt/opendaylight/bin/setenv: line 61: EXTRA_JAVA_OPTS:: not found
Traceback (most recent call last):
File "/opt/onap/sdnc/bin/installCerts.py", line 33, in <module>
with open(os.path.join('/opt/opendaylight/data/log', 'installCerts.log'), 'w') as fp:
IOError: [Errno 2] No such file or directory: '/opt/opendaylight/data/log/installCerts.log'
Apache Karaf starting up. Press Enter to open the shell now...
100% [========================================================================]
Karaf started in 0s. Bundle stats: 12 active, 12 total
however from a k8s perspective I have no error
kubectl get pods -n onap |grep sdnc
onap-sdnc-0 2/2 Running 0 5h29m
onap-sdnc-ansible-server-59d9fcc479-tnw8z 1/1 Running 0 5h29m
onap-sdnc-db-0 1/1 Running 0 5h29m
onap-sdnc-dbinit-job-sxg4c 0/1 Completed 0 5h29m
onap-sdnc-dgbuilder-f5b58ff5-jz5cg 1/1 Running 0 5h29m
onap-sdnc-dmaap-listener-59bcfff5c9-dxs8k 1/1 Running 0 5h29m
onap-sdnc-ueb-listener-74d94b6495-jlbwf 1/1 Running 2 5h29m
onap-so-sdnc-adapter-75b96bc658-7d6s2 2/2 Running 0 5h21m
onap-vfc-zte-sdnc-driver-78b8d9c7d9-pqvvw 1/1 Running 0 5h16m
I restarted the pod and I got the same error
Did you already get this error?
As it is the first time, I did not create a JIRA yet
I would like to be sure it is reproducible..or not
I did not see any recent patch on OOM/frankfurt that could explain this.
versions on the daily
sdnc | sdnc | nexus3.onap.org:10001/onap/sdnc-image | 1.8.2 |
sdnc | filebeat-onap | docker.elastic.co/beats/filebeat | 5.5.0 |
sdnc-ansible-server | sdnc-ansible-server | nexus3.onap.org:10001/onap/sdnc-ansible-server-image | 1.8.2 |
onap-sdnc-db | sdnc-db | nexus3.onap.org:10001/adfinissygroup/k8s-mariadb-galera-centos | v002 |
sdnc-job | sdnc | nexus3.onap.org:10001/onap/sdnc-image | 1.8.2 |
sdnc-dgbuilder | sdnc-dgbuilder | nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image | 0.7.2 |
sdnc-dmaap-listener | sdnc-dmaap-listener | nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image | 1.8.2 |
sdnc-ueb-listener | sdnc-ueb-listener | nexus3.onap.org:10001/onap/sdnc-ueb-listener-image | 1.8.2 |