Hi SDNC Team,

We see that SDNC re-deployment on an existing ONAP fails to bring up some
of the core services and PODs.


Here are the steps that we performed. The issue seems to be more to do with
SDNC dependent charts. We would appreciate any help to resolve this one.


1) Undeploy SDNC alone


    helm undeploy dev-sdnc --purge


     # We did patch PV and PVC to make sure all k8s resources are deleted


2) My sdnc-overrides.yaml



   global:

      debugEnabled: true

      flavor: unlimited

      enabled: true


3) Deploy SDNC

    helm deploy dev-sdnc local/sdnc --namespace onap --timeout 900
--verbose -f

    /home/aarna/onap-custom/util-scripts/templates/sdnc-overrides.yaml


4) The above command only brings CDS and SDNC controller PODs


    dev-sdnc-cds-cds-blueprints-processor-79f4cbd6cc-wwd4z       0/1
Init:0/1 0 2m42s

    dev-sdnc-cds-cds-command-executor-6bd5d966c6-9th9l           0/1
Init:0/1 0 2m42s

    dev-sdnc-cds-cds-controller-blueprints-5bb4988f59-p64tl      0/1
Init:0/1 0 2m42s

    dev-sdnc-cds-cds-db-0                                        1/1
Running 0 2m42s

    dev-sdnc-cds-cds-sdc-listener-78444f899d-xhjzm               0/1
Init:0/1 0 2m42s

    dev-sdnc-cds-cds-ui-c9dd576cd-k7h6v                          1/1
Running 0 2m42s

    dev-sdnc-sdnc-0                                              0/2
Init:0/2 0 2m44s


5) Helm list shows that dev-sdnc failed status


     helm list | grep sdnc


dev-sdnc          3       Wed Nov  6 17:11:41 2019 *FAILED*  sdnc-4.0.0
                onap

dev-sdnc-cds      1       Wed Nov  6 17:05:46 2019 DEPLOYED cds-4.0.0
              onap


6) We don't get the below PODs, even after performing the upgrade


dev-sdnc-nengdb-0

dev-sdnc-network-name-gen-XX

dev-sdnc-sdnc-ansible-server-XX

dev-sdnc-sdnc-dgbuilder-XX

dev-sdnc-sdnc-dmaap-listener-XX

dev-sdnc-sdnc-ueb-listener-XX


7) Below upgrade command failed with error


     helm upgrade dev-sdnc local/sdnc --namespace onap --timeout 900 -f

     /home/aarna/onap-custom/util-scripts/templates/sdnc-overrides.yaml



      Error: UPGRADE FAILED: no Service with the name "
*cds-blueprints-processor-grpc*" found



8) But we have the following services

    *cds-blueprints-processor-grpc*      ClusterIP 10.43.150.206 <none>
                            9111/TCP 4m24s

    cds-blueprints-processor-http      NodePort 10.43.42.54 <none>
                        8080:30499/TCP 4m24s

    cds-command-executor               ClusterIP 10.43.6.237 <none>
                        50051/TCP 4m23s

    cds-controller-blueprints          ClusterIP 10.43.143.93 <none>
                          8080/TCP 4m23s

    cds-db                             ClusterIP None <none>
                  3306/TCP 4m23s

    cds-sdc-listener                   ClusterIP 10.43.94.186 <none>
                          8080/TCP 4m23s

    cds-ui                             NodePort 10.43.83.7 <none>
                      3000:30497/TCP


9) Tried with --force option fails with different error


   helm upgrade dev-sdnc local/sdnc --namespace onap --timeout 900 -f
/home/aarna/onap-custom/util-scripts/templates/sdnc-overrides.yaml --force


Error: UPGRADE FAILED: no Secret with the name "*dev-sdnc-cds-db*" found


   # We do see the following secret dev-sdnc-cds-db

dev-sdnc-cds-cds-db                                     Opaque 2 6m12s

*dev-sdnc-cds-db*                                         Opaque 2 2m39s

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#19360): https://lists.onap.org/g/onap-discuss/message/19360
Mute This Topic: https://lists.onap.org/mt/44359821/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to