Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

CSIT/CCSDK Automation Issues

...


Where were we?

Using SDNC v1.8.1 & certs that we have in our repo we were able to use SDNC, mount nodes, & retrieve information using /rests & /restconf

...

Our integration (and manual) testing using SDN-C v.1.8.1 worked fine. At a high level the setup followed these steps

  1. pre-generated (?) zip (csit/plans/cps/sdnc/certs) extract to /opt/opendaylight/current/certs 
  2. Install SDN-C v 1.8.1
  3. Mount a node
  4. Execute /rests and /restconf requests to nodes successfully either manual and directly to SND-C or using CPS services


Code Block
languageyml
titleOld CPS SDNC docker-compose.yml
linenumberstrue
collapsetrue
# ============LICENSE_START=======================================================
# Copyright (C) 2021 Nordix Foundation
# ================================================================================
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#       http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# ============LICENSE_END=========================================================

version: '3'

services:
  mariadb:
    image: mariadb:10.1.11
    ports:
      - "3306:3306"
    container_name: mariadb
    environment:
      - MYSQL_ROOT_PASSWORD=password
    hostname:
      mariadb.so.testlab.onap.org
    logging:
      driver: "json-file"
      options:
        max-size: "30m"
        max-file: "5"
  sdnc:
    image: onap/sdnc-image:1.8.1
    container_name: sdnc
    volumes: 
      - /etc/localtime:/etc/localtime:ro
      - ./certs:/opt/opendaylight/current/certs
    entrypoint: ["/opt/onap/sdnc/bin/startODL.sh"]
    ports:
      - "8282:8181"
    hostname:
      sdnc
    depends_on:
      - mariadb
    environment:
      - MYSQL_ROOT_PASSWORD=password
      - SDNC_CONFIG_DIR=/opt/onap/sdnc/data/properties
      - MYSQL_PASSWD=password
      - ODL_CERT_DIR=/opt/opendaylight/current/certs
      - ODL_ADMIN_USERNAME=admin
      - ODL_ADMIN_PASSWORD=Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U
    dns:
      - ${DNS_IP_ADDR-10.0.100.1}
    logging:
      driver:   "json-file"
      options:
        max-size: "30m"
        max-file: "5"
    extra_hosts:
      - sdnctldb02:${LOCAL_IP}
      - sdnctldb01:${LOCAL_IP}
      - dbhost:${LOCAL_IP}

Where are we now?

...

  1. Installing pre-existing certs caused issues with SDN-C v. 2.2.3

...

  1. installation, so we removed this step[ (we assume it now includes its own certs)
  2. Install SDN-C (output includes details on ODL certification installation)

    Code Block
    languageyml
    titleSDNC Certificate Success
    collapsetrue
    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 


  3. Mount Node
  4. 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

    Image Modified
    the nodes can also be retrieved using /restconf
    Image Modified

...


  1. /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
    languageyml
    titlePostman Response
    linenumberstrue
    {
        "errors": {
            "error": [
                {
                    "error-tag": "resource-denied-transport",
                    "error-type": "protocol",
                    "error-message": "Mount point does not exist."
                }
            ]
        }
    }

...


  1. CPS CSIT test fail with same root cause
Info
iconfalse
titleCSIT 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."}]}}]

Summary

Perhaps there is a change in the way /rests behaves that we are unfamilar 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.

...