The VNFM pod is a work in progress, you should be ok right now to run most use cases.
Thanks -Steve From: <[email protected]> on behalf of David Darbinyan <[email protected]> Reply-To: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Date: Thursday, April 11, 2019 at 5:54 AM To: "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, "PLATANIA, MARCO" <[email protected]> Subject: Re: [onap-discuss] ONAP SO hi Marco Though it seems to be working after 1-6, but in stacked again on Crashed pod. Here what we have (i'm with Rudolf ). last pod is in CrashLoopBackOff status. pls advise onap development-so-so-846648cb94-jfp4n 1/1 Running 0 1d 10.42.177.63 srv15 onap development-so-so-bpmn-infra-7f489879cb-jbzww 1/1 Running 0 1d 10.42.208.222 srv15 onap development-so-so-catalog-db-adapter-5967dcf78f-rlpvx 1/1 Running 0 1d 10.42.18.174 srv13 onap development-so-so-mariadb-74654f9db5-wd9xk 1/1 Running 1 1d 10.42.218.52 srv11 onap development-so-so-monitoring-564984886b-lkqh5 1/1 Running 0 1d 10.42.95.5 srv15 onap development-so-so-openstack-adapter-647475d789-z558f 1/1 Running 3 1d 10.42.131.38 srv13 onap development-so-so-request-db-adapter-5fcc864469-dvq58 1/1 Running 0 1d 10.42.223.179 srv11 onap development-so-so-sdc-controller-b4b4967cf-kpvdd 1/1 Running 0 1d 10.42.156.130 srv15 onap development-so-so-sdnc-adapter-7bb9d795b6-jwx8n 1/1 Running 0 1d 10.42.111.97 srv13 onap development-so-so-vfc-adapter-7c9fd654bb-stdll 1/1 Running 1 1d 10.42.96.68 srv11 onap development-so-so-vnfm-adapter-676f9fb447-7hb96 0/1 CrashLoopBackOff 270 1d 10.42.229.86 srv11 Regards On 4/10/19 11:59 AM, Rudolf Amirjanyan wrote: Hi Marco, Thanks for your detailed explanation... did 1 -6 steps, (I mean even did not deleted SO pods, )and it works. Regards, Rudolf On 4/9/19 4:12 PM, PLATANIA, MARCO (MARCO) wrote: Rudolf, This issue is described here: https://jira.onap.org/browse/SO-1674<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_SO-2D1674&d=DwMDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=shs6nPzThSiGJml9VXN0Eg&m=2Hx1eZL_ED7ift1j5IfePwK-rhHTzv9Yq7VVxbeL0Hc&s=jLPF8-V8CcyeGpuDCaASdpEOCon_rxVErGPwU-WJ1h8&e=> Here’s the workaround: 1. Connect to MariaDB container 2. mysql -uroot 3. use mysql; 4. SET PASSWORD FOR 'root'@'localhost' = PASSWORD('password'); 1. cd docker-entrypoint-initdb.d 2. Run scripts 01-… to 05-… 3. Delete SO pods without deleting NFS data and recreate Marco From: <[email protected]><mailto:[email protected]> on behalf of Rudolf Amirjanyan <[email protected]><mailto:[email protected]> Reply-To: "[email protected]"<mailto:[email protected]> <[email protected]><mailto:[email protected]>, "[email protected]"<mailto:[email protected]> <[email protected]><mailto:[email protected]> Date: Tuesday, April 9, 2019 at 1:01 AM To: "[email protected]"<mailto:[email protected]> <[email protected]><mailto:[email protected]> Subject: [onap-discuss] ONAP SO Hi, after installing ONAP SO, I get only 3 running pods.. the rest are getting status "CrashLoopBackOff"...(see screen shot) I have tried both, "Casablanca" and "Dublin" versions and get same result... Is there any trick to make it working ? thanks. -- -- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16523): https://lists.onap.org/g/onap-discuss/message/16523 Mute This Topic: https://lists.onap.org/mt/30996141/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
