...
CSIT/CCSDK Automation Issues
...
Ticket logged:
Jira | ||||||
---|---|---|---|---|---|---|
|
Where were we?
Our integration (and manual) testing using SDN-C v.1.8.1 worked fine. At a high level the setup followed these steps
...
Installing pre-existing certs.This caused issues with SDN-C v. 2.2.3 installation, so we removed this step[ (we assume SDN-C now includes its own and/or ODL certs)Install SDN-C (output includes details on ODL certification installation)
Code Block language yml title SDNC Certificate Success collapse true 100% [========================================================================] Karaf started in 44s. Bundle stats: 433 active, 434 total Certificate installation in progress. Elapsed time - 60 secs. Waiting for 10 secs before checking the status.. Certificate installation in progress. Elapsed time - 70 secs. Waiting for 10 secs before checking the status.. Certificate installation in progress. Elapsed time - 80 secs. Waiting for 10 secs before checking the status.. Certificate installation in progress. Elapsed time - 90 secs. Waiting for 10 secs before checking the status.. Start cert provisioning. Log file: /opt/opendaylight/current/data/log/installCerts.log Certificate installation script completed execution Everything OK in Certificate Installation
- Mount Node
- RestConf queries work fine:
We can also query SDNC to return all nodes using http://localhost:8282/restconf/config/network-topology:network-topology/topology/topology-netconf
the nodes can also be retrieved using /restconf /rest based request fail
http://localhost:8282/rests/data/network-topology:network-topology/topology=topology-netconf/node=DemoNode/yang-ext:mount/turing-machine:turing-machine we receive the following error:Code Block language yml title Postman Response linenumbers true { "errors": { "error": [ { "error-tag": "resource-denied-transport", "error-type": "protocol", "error-message": "Mount point does not exist." } ] } }
CPS CSIT test fail with same root cause
Info icon false title CSIT Error 09:49:08.028 [http-nio-8080-exec-8] ERROR o.o.c.n.d.e.DmiExceptionHandler - Exception occurred
org.springframework.web.client.HttpServerErrorException$ServiceUnavailable: 503 Service Unavailable: [{"errors":{"error":[{"error-tag":"resource-denied-transport","error-type":"protocol","error-message":"Mount point does not exist."}]}}]
...
Perhaps there is a change in the way /rests behaves that we are unfamiliar with or perhaps our configuration is incorrect. To sum up: we can successfully start SDNC, mount a node, query nodes using /restconf but all /rests calls seem to fail. This could be an issue with certs or TLS.
Open Questions
# | Question/Issue | Notes/Decision | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Are we to generate certs for SDNC ourselves or can we rely on the certs used as part of SDNC itself? | As mentioned on https://docs.onap.org/projects/onap-sdnc-oam/en/istanbul/cert_installation.html certs folder is required as part of installing SDNC through docker-compose | ||||||||||
2 | Do we have some incorrect config in our docker-compose file?
|
Using the docker-compose file wherein the certs folder is specified through volume mount, we are able to mount and access nodes directly through SDNC but fails through NCMP
Need mount to specific files, see https://gerrit.onap.org/r/c/cps/+/126945/14..15/csit/plans/cps/sdnc/docker-compose.yml Original guide used for sdnc docker-compose can be found here: Istanbul - Run. | |
3 |
CPS has certs within our repo which were generated for previous versions of SDNC. If we mount the volume as such: volumes: 18:23:42 2022-02-07 18:09:57,310 - root - ERROR - Error while extracting zip file(s). Exiting Certificate Installation. This is how we installed and used certs for SDNC 1.8.1 so has the process of accessing the certs changed? | This was resolved by adding separate volume mounts for the files contained with the certs folder. Old:
New:
|