The problem seems related to https://jira.onap.org/browse/SO-1515
Please note docker-manifest-staging has higher version of so images than OOM charts right now. The jira above was using version in docker-manifest-staging.csv. Regards, -Yang From: [email protected] [mailto:[email protected]] On Behalf Of Michael O'Brien Sent: Monday, February 18, 2019 2:12 PM To: [email protected]; [email protected] Subject: Re: [onap-discuss] so-mariadb pod is not initialized properly. #casablanca (initial threat: SO issues about certificates during installation ) #SO Guys, just an observation, besides whether the config job actually runs the db config properly – I don’t see any issue with the pods themselves in master or Casablanca (testing other issues – so I had these results handy – for single component deploys) If you are seeing intermittent issues – it may be timing related on your system – do you see the same issue if you just bring up SO by itself (note that SO currently has no enforced pod dependencies to dmaap for example) All my SO pods are up fine master amdocs@obriensystemsu0:~$ kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system heapster-7b48b696fc-69hqm 1/1 Running 0 12h kube-system kube-dns-6655f78c68-blgzk 3/3 Running 0 12h kube-system kubernetes-dashboard-6f54f7c4b-69hd2 1/1 Running 0 12h kube-system monitoring-grafana-7877679464-fmwws 1/1 Running 0 12h kube-system monitoring-influxdb-64664c6cf5-kqswn 1/1 Running 0 12h kube-system tiller-deploy-6f4745cbcf-p55ng 1/1 Running 0 12h onap onap-dmaap-dbc-pg-0 1/1 Running 0 7h onap onap-dmaap-dbc-pg-1 1/1 Running 0 7h onap onap-dmaap-dbc-pgpool-d865b8fdd-7n8lh 1/1 Running 0 7h onap onap-dmaap-dbc-pgpool-d865b8fdd-rmndq 1/1 Running 0 7h onap onap-dmaap-dmaap-bus-controller-776674db7f-qqr64 1/1 Running 0 7h onap onap-dmaap-dmaap-dr-db-0 1/1 Running 0 7h onap onap-dmaap-dmaap-dr-db-1 1/1 Running 0 7h onap onap-dmaap-dmaap-dr-node-57f77bd54d-jqlvk 0/1 Running 122 7h onap onap-dmaap-dmaap-dr-prov-5987c4898c-hqb48 1/1 Running 0 7h onap onap-dmaap-message-router-0 1/1 Running 0 7h onap onap-dmaap-message-router-kafka-0 1/1 Running 2 7h onap onap-dmaap-message-router-kafka-1 1/1 Running 2 7h onap onap-dmaap-message-router-kafka-2 1/1 Running 2 7h onap onap-dmaap-message-router-zookeeper-0 1/1 Running 0 7h onap onap-dmaap-message-router-zookeeper-1 1/1 Running 0 7h onap onap-dmaap-message-router-zookeeper-2 1/1 Running 0 7h onap onap-robot-robot-64886c7774-92vqq 1/1 Running 0 7h onap onap-so-so-75bb4b68bb-88xx7 1/1 Running 0 7h onap onap-so-so-bpmn-infra-56f99599b6-4x47n 1/1 Running 0 7h onap onap-so-so-catalog-db-adapter-7994778fd9-ll9hf 1/1 Running 0 7h onap onap-so-so-mariadb-795cf844d8-g6msl 1/1 Running 0 7h onap onap-so-so-monitoring-b75b95f76-xbv5q 1/1 Running 0 7h onap onap-so-so-openstack-adapter-78dc84b88f-5jjhm 1/1 Running 1 7h onap onap-so-so-request-db-adapter-64ff55cb79-pn4c8 1/1 Running 0 7h onap onap-so-so-sdc-controller-d89d44595-8k24j 1/1 Running 0 7h onap onap-so-so-sdnc-adapter-8db65dfb8-w6c27 1/1 Running 0 7h onap onap-so-so-vfc-adapter-6c4d54b6fd-z88hx 1/1 Running 0 7h casablanca 20190218 amdocs@obriensystemsu0:~$ kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system heapster-7b48b696fc-69hqm 1/1 Running 0 17h kube-system kube-dns-6655f78c68-blgzk 3/3 Running 0 17h kube-system kubernetes-dashboard-6f54f7c4b-69hd2 1/1 Running 0 17h kube-system monitoring-grafana-7877679464-fmwws 1/1 Running 0 17h kube-system monitoring-influxdb-64664c6cf5-kqswn 1/1 Running 0 17h kube-system tiller-deploy-6f4745cbcf-p55ng 1/1 Running 0 17h onap onap-dmaap-dbc-pg-0 1/1 Running 0 3h onap onap-dmaap-dbc-pg-1 1/1 Running 0 3h onap onap-dmaap-dbc-pgpool-d865b8fdd-wxcgl 1/1 Running 0 3h onap onap-dmaap-dbc-pgpool-d865b8fdd-zqbnw 1/1 Running 0 3h onap onap-dmaap-dmaap-bus-controller-776674db7f-l82kw 1/1 Running 0 3h onap onap-dmaap-dmaap-dr-db-0 1/1 Running 0 3h onap onap-dmaap-dmaap-dr-db-1 1/1 Running 0 3h onap onap-dmaap-dmaap-dr-node-57f77bd54d-p6lh4 0/1 Running 58 3h onap onap-dmaap-dmaap-dr-prov-5987c4898c-5bmhl 1/1 Running 0 3h onap onap-dmaap-message-router-0 1/1 Running 0 3h onap onap-dmaap-message-router-kafka-0 1/1 Running 2 3h onap onap-dmaap-message-router-kafka-1 1/1 Running 2 3h onap onap-dmaap-message-router-kafka-2 1/1 Running 2 3h onap onap-dmaap-message-router-zookeeper-0 1/1 Running 0 3h onap onap-dmaap-message-router-zookeeper-1 1/1 Running 0 3h onap onap-dmaap-message-router-zookeeper-2 1/1 Running 0 3h onap onap-robot-robot-64886c7774-kpdhf 1/1 Running 0 3h onap onap-so-so-75bb4b68bb-755ww 1/1 Running 0 3h onap onap-so-so-bpmn-infra-56f99599b6-jhx7z 1/1 Running 0 3h onap onap-so-so-catalog-db-adapter-7994778fd9-rjbjz 1/1 Running 0 3h onap onap-so-so-mariadb-795cf844d8-g7bps 1/1 Running 0 3h onap onap-so-so-monitoring-b75b95f76-vwj87 1/1 Running 0 3h onap onap-so-so-openstack-adapter-78dc84b88f-m555v 1/1 Running 1 3h onap onap-so-so-request-db-adapter-64ff55cb79-fxmsj 1/1 Running 0 3h onap onap-so-so-sdc-controller-d89d44595-hsncg 1/1 Running 0 3h onap onap-so-so-sdnc-adapter-8db65dfb8-68h9q 1/1 Running 0 3h onap onap-so-so-vfc-adapter-6c4d54b6fd-rzhc8 1/1 Running 0 3h From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of D'Alessandro Alessandro Gerardo Sent: Monday, February 18, 2019 11:39 AM To: D'Alessandro Alessandro Gerardo <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] so-mariadb pod is not initialized properly. #casablanca (initial threat: SO issues about certificates during installation ) #SO Hi all, after having investigated further more our issue, it seems to be similar to the one described here: https://lists.onap.org/g/onap-discuss/message/14817 In fact, we discovered that so-mariadb pod was not configured correctly during the automated installation process. So, we ran the following script: 1. [root@mariadb:/docker-entrypoint-initdb.d] ./01-create-camundabpmn.sh fails with the error ERROR 1396 (HY000) at line 4: Operation CREATE USER failed for 'camundauser'@'%' 2. [root@mariadb:/docker-entrypoint-initdb.d] ./02-create-requestdb.sh -> OOK 3. [root@mariadb:/docker-entrypoint-initdb.d] ./03-create-catalogdb.sh --> OOK 4. [root@mariadb:/docker-entrypoint-initdb.d] ./04-create-so-user.sh --> OOK 5. [root@mariadb:/docker-entrypoint-initdb.d] ./05-create-so-admin.sh --> OOK After the steps above, all SO pods are into the running state except dev-so-bpmn-infra- that remains into the CrashLoopBackOff state. any suggestion to fix that issue would be appreciated. thanks a lot. Alessandro This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15621): https://lists.onap.org/g/onap-discuss/message/15621 Mute This Topic: https://lists.onap.org/mt/29900631/21656 Mute #so: https://lists.onap.org/mk?hashtag=so&subid=2740164 Mute #casablanca: https://lists.onap.org/mk?hashtag=casablanca&subid=2740164 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
