SMO Installation

hello experts,

after onap deployment, i have a pod not ready but completed, is it normal? thanks

dev-sdnc-sdnrdb-init-job-6v525 0/1 Completed 0 18m 10.244.0.159 smobronze <none> <none>

and is it possible to set the pullPolicy to IfNotPresent for all the charts of onap?

Hi. I am new to O-RAN and trying to deploy SMO as well as RIC. I was successfully able to install SMO with the given steps but while deploying I keep on getting below messages:-

===> Deploying OAM (ONAP Lite)
======> Deploying ONAP-lite
Error: unknown command "deploy" for "helm"
Run 'helm --help' for usage.
======> Waiting for ONAP-lite to reach operatoinal state
0/7 SDNC-SDNR pods and 0/7 Message Router pods running
0/7 SDNC-SDNR pods and 0/7 Message Router pods running
0/7 SDNC-SDNR pods and 0/7 Message Router pods running

None of these pods are getting up and running for like hours, infact none of them are even present. Did I miss any step or do i need to install any component of ONAP before this?

Hello experts ,

I  followed it step by step but I stuck by step 3 .

When I Run the script, k8s-1node-cloud-init-k ... .sh, I received the following message. 

The connection to the server localhost:8080 was refused - did you specify the right host or port? 

I don't know if I did something wrong or if I missed something I need to pay attention . 

How can I fix it, Thank you .

Tim.

Hello there,

In step-2, when I execute the script, "gen-cloud-init.sh" after editing the 'infra.rc' file, it throws "cannot execute binary file" output as follows:

./gen-cloud-init.sh: line 39: source: /home/airvana/dep/tools/k8s/bin/../etc/.infra.rc.swo: cannot execute binary file

./gen-cloud-init.sh: line 39: source: /home/airvana/dep/tools/k8s/bin/../etc/.infra.rc.swl: cannot execute binary file

./gen-cloud-init.sh: line 39: source: /home/airvana/dep/tools/k8s/bin/../etc/.infra.rc.swp: cannot execute binary file

./gen-cloud-init.sh: line 39: source: /home/airvana/dep/tools/k8s/bin/../etc/.infra.rc.swn: cannot execute binary file

./gen-cloud-init.sh: line 39: source: /home/airvana/dep/tools/k8s/bin/../etc/.infra.rc.swm: cannot execute binary file

If I assume that is normal and move on to step-3 to execute "k8s-1node-cloud-init-k_1_15-h_2_16-d_18_09.sh",  It throws the following errors:

The connection to the server localhost:8080 was refused - did you specify the right host or port?
+ kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
unable to recognize "https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp 127.0.0.1:8080: connect: connection refused

And then following, 

+++ kubectl get pods -n kube-system
+++ grep Running
+++ wc -l
The connection to the server localhost:8080 was refused - did you specify the right host or port?
+ NUMPODS=0
+ echo '> waiting for 0/8 pods running in namespace [kube-system] with keyword [Running]'
> waiting for 0/8 pods running in namespace [kube-system] with keyword [Running]
+ '[' 0 -lt 8 ']'

I am a novice in these technologies, your help would be much appreciated.

Thank you.

Hi,

After deploying SMO, how can I open O1 dashboard? I tried opening http://localhost:8181/odlux/index.html but receiving "connection refused". Can anyone please help?

Dear all,

I am getting the following error:

Creating /root/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Error: error initializing: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Failed to fetch https://kubernetes-charts.storage.googleapis.com/index.yaml : 403 Forbidden

It seems some URLs may not be valid anymore?

Any help would be appreciated.

BR

Daniel

Hi 

If any of us as the normal users (out of this PL team) can really make this up and running?!???????

Full of errors and even more errors after checking and applying this cummunity "answers"

Very disapointed, Sorry but this is true !!!

Hi,

I am following deployment steps for SMO. Upon running the k8s-1node-cloud-init-k_1_15-h_2_16-d_18_09.sh script, I come across the following error. Kindly share the solution if anyone has found it.

E: Version '18.09.7-0ubuntu1~18.04.4' for 'docker.io' was not found
+ cat
./k8s-1node-cloud-init-k_1_15-h_2_16-d_18_09.sh: line 156: /etc/docker/daemon.json: No such file or directory
+ mkdir -p /etc/systemd/system/docker.service.d
+ systemctl enable docker.service
Failed to enable unit: Unit file docker.service does not exist.

Hello,

I have come across the following error while installing SMO.  if anyone has a solution for it, kindly share the same.

Creating /root/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Error: error initializing: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Failed to fetch https://kubernetes-charts.storage.googleapis.com/index.yaml : 403 Forbidden
+ helm init -c
Creating /root/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Error: error initializing: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Failed to fetch https://kubernetes-charts.storage.googleapis.com/index.yaml : 403 Forbidden

Regards,

Pavan

Dear all,

After following the indicated steps (using helm 2.17.0 to avoid an error), the deployment of dev-sdnc fails and I get stuck here:

======> Deploying ONAP-lite
fetching local/onap
release "dev" deployed
release "dev-consul" deployed
release "dev-dmaap" deployed
release "dev-mariadb-galera" deployed
release "dev-msb" deployed
release "dev-sdnc" deployed
dev-sdnc 1 Sat Jan 9 12:18:06 2021 FAILED sdnc-6.0.0 onap
======> Waiting for ONAP-lite to reach operatoinal state
0/7 SDNC-SDNR pods and 0/7 Message Router pods running
0/7 SDNC-SDNR pods and 0/7 Message Router pods running
0/7 SDNC-SDNR pods and 0/7 Message Router pods running

...

Any help would be appreciated.

BR

Daniel

Hi All,

Is there a slack group for discussions ?

Thanks,

Naga chetan

Hello,

SMO installation was successful. I have run it on AWS instance. Any idea how one can check out SMO functioning? I mean any curl command or web page that can be tried?

Pavan

Good Updates: After >10 times, I finally came up with this combination, and it worked for me:

• My Ubuntu Desktop: 18.04.2
• I followed the initial instruction above
• And I followed Javi G recommendations to go to "k8s..." file to change the below:

  • Use: "19.03.6" for docker: echo "19.03.6" > /opt/config/docker_version.txt

  • Use: "2.17.0" for heml
  • DOCKERVERSION="${DOCKERV}-0ubuntu1~18.04.3 ### (Note that: I entered: 18.04.3 even though my  Ubuntu Desktop is: 18.04.2)

Thank you Javi G.

I hope the new comers can make this works, or try to use the above combination to make it work

After Step 1 and Before Step #2 Change the following files

dep/tools/k8s/etc/infra.rc

dep/tools/k8s/heat/scripts/k8s_vm_install.sh

dep/smo/bin/install

Then run Step #2, Step #3 and Step #4 normally.

Hi,

   I need help on running dcaemod using SMO Lite . Can i know what all other ONAP components should be enabled for running dcaemod ? Any kind of dependency on other modules of ONAP

I've started to deploy SMO with ubuntu 20.04 desktop but an error ocurrs when try to install smo.

It's not allow this last ubuntu version?

hi every,

i execute this instruction,kubectl get pods --all-namespaces,

but i got one place strange, I have tag it into red .

Could anyone help me to solve this problem?

NAMESPACE NAME READY STATUS RESTARTS AGE

kube-system coredns-5d4dd4b4db-82gnh 1/1   Running   2 128m

kube-system coredns-5d4dd4b4db-8mrqh 1/1   Running   2 128m

kube-system etcd-smo-virtualbox 1/1   Running   2 127m

kube-system kube-apiserver-smo-virtualbox 1/1   Running   2 127m

kube-system kube-controller-manager-smo-virtualbox 1/1   Running   2 127m

kube-system kube-flannel-ds-9xr8x 1/1   Running   2 128m

kube-system kube-proxy-lwmnh 1/1 Running 2 128m

kube-system kube-scheduler-smo-virtualbox 1/1 Running 2 127m

kube-system tiller-deploy-7c54c6988b-jgrqg 1/1 Running 2 127m

nonrtric a1-sim-osc-0 1/1 Running 0 16m

nonrtric a1-sim-osc-1 1/1 Running 0 4m47s

nonrtric a1-sim-std-0 1/1 Running 0 16m

nonrtric a1-sim-std-1 1/1 Running 0 5m6s

nonrtric a1-sim-std2-0 1/1 Running 0 16m

nonrtric a1-sim-std2-1 1/1 Running 0 15m

nonrtric a1controller-64c4f59fb5-tdllp 1/1 Running 0 16m

nonrtric controlpanel-78f957844b-nb5qc 1/1 Running 0 16m

nonrtric db-549ff9b4d5-58rmc 1/1 Running 0 16m

nonrtric enrichmentservice-7559b45fd-2wb7p 1/1 Running 0 16m

nonrtric nonrtricgateway-6478f59b66-wjjkz 1/1 Running 0 16m

nonrtric policymanagementservice-79f8f76d8f-ch46v 1/1 Running 0 16m

nonrtric rappcatalogueservice-5945c4d84b-7w7cc 1/1 Running 0 16m

onap dev-consul-68d576d55c-l2n2q 1/1 Running 0 53m

onap dev-consul-server-0 1/1 Running 0 53m

onap dev-consul-server-1 1/1 Running 0 52m

onap dev-consul-server-2 1/1 Running 0 52m

onap dev-kube2msb-9fc58c48-s5g98 1/1 Running 0 52m

onap dev-mariadb-galera-0 1/1 Running 0 53m

onap dev-mariadb-galera-1 1/1 Running 0 46m

onap dev-mariadb-galera-2 1/1 Running 0 39m

onap dev-message-router-0 1/1 Running 0 53m

onap dev-message-router-kafka-0 1/1 Running 0 53m

onap dev-message-router-kafka-1 1/1 Running 0 53m

onap dev-message-router-kafka-2 1/1 Running 0 53m

onap dev-message-router-zookeeper-0 1/1 Running 0 53m

onap dev-message-router-zookeeper-1 1/1 Running 0 53m

onap dev-message-router-zookeeper-2 1/1 Running 0 53m

onap dev-msb-consul-65b9697c8b-6hhck 1/1 Running 0 52m

onap dev-msb-discovery-54b76c4898-xz7rq 2/2 Running 0 52m

onap dev-msb-eag-76d4b9b9d7-jfms9 2/2 Running 0 52m

onap dev-msb-iag-65c59cb86b-864jr 2/2 Running 0 52m

onap dev-sdnc-0 2/2 Running 0 52m

onap dev-sdnc-db-0 1/1 Running 0 52m

onap dev-sdnc-dmaap-listener-5c77848759-svmzg 1/1 Running 0 52m

onap dev-sdnc-sdnrdb-init-job-d6rjm 0/1 Completed 0 41m

onap dev-sdnc-sdnrdb-init-job-qkdl8 0/1 Init:Error 0 52m

onap dev-sdnrdb-coordinating-only-9b9956fc-zjqkg 2/2 Running 0 52m

onap dev-sdnrdb-master-0 1/1 Running 0 52m

onap dev-sdnrdb-master-1 1/1 Running 0 40m

onap dev-sdnrdb-master-2 1/1 Running 0 38m

ricaux bronze-infra-kong-68657d8dfd-d5bb4 2/2 Running 1 4m57s

ricaux deployment-ricaux-ves-65db844758-td2zc 1/1 Running 0 4m47s

BR,

Tim

There seems to be a mismatch in the VM minimum requirements on this page and the PDF linked in that section. The RAM required is mentioned as 32 GB and the CPU cores as 8; however, the "Getting Started PDF" mentions the required RAM as 16 GB and CPU cores as 4. So how much minimum RAM and CPU cores does the SMO VM actually require? Also, if these are the minimum requirements, what are the standard or recommended VM requirements? I suspect that the Getting Started PDF for Near Realtime RIC installation has been mistakenly linked here. Could someone confirm this?

Thanks,

Vikas Krishnan

Hello guys,

In step 3, i have this problem:  

++ eval 'kubectl get pods -n kube-system | grep "Running" | wc -l'

+++ wc -l

+++ grep Running

+++ kubectl get pods -n kube-system

The connection to the server localhost:8080 was refused - did you specify the right host or port?

+ NUMPODS=0

+ echo '> waiting for 0/8 pods running in namespace [kube-system] with keyword [Running]'

> waiting for 0/8 pods running in namespace [kube-system] with keyword [Running]

+ '[' 0 -lt 8 ']'

+ sleep 5

I tried to solve this problem by reading the comments related to this subject but this issue still remains...
My Ubuntu version is 18.04.1 LTS and i follow the previous steps.

Can someone help please?!

Rafael

Hi All

I am trying to install cherry release. However compared to bronze I don't see "dep/smo/bin" folder anymore. So I can't run the install command. Can anyone suggest alternative? All steps till step-3 is successful, only step-4 is not valid for cherry release.

Seemly, the mismatch between k8s version , docker version and helm version is causing many issues. Could anyone update the latest load line? I'm using Ubuntu server 18.04.05 and not able to done the steps successfully. 

Can the SMO be deployed on AWS EKS or on Google Kubernetes Engine? Has someone already tried this?

Hi Experts,

While running the install script getting below error

error: resource(s) were provided, but no name, label selector, or --all flag specified
error: resource(s) were provided, but no name, label selector, or --all flag specified
======> Clearing out all RICAUX deployment resources
Error from server (NotFound): namespaces "ricaux" not found
Error from server (NotFound): namespaces "ricinfra" not found
======> Clearing out all NONRTRIC deployment resources
Error from server (NotFound): namespaces "nonrtric" not found
======> Preparing for redeployment

1) Also tiller pod is running 

kube-system tiller-deploy-7d7bc87bb-fvr6v 1/1 Running 1 23h

2) helm search onap | wc -l' has 35 charts listed after manually 'make all' command.

Please next action plan to solve the problem.

Br

Deepak

Hello,

I am having issues with nonrtric pods/ This is an output of errors in install script:

===> Deploy NONRTRIIC

...

Error: open /root/.helm/repository/local/index.yaml: no such file or directory

+ cp /tmp/nonrtric-common-2.0.0.tgz /root/.helm/repository/local/

+ helm repo index /root/.helm/repository/local/

+ helm repo remove local

Error: no repo named "local" found
+ helm repo add local http://127.0.0.1:8879/charts
"local" has been added to your repositories

...

Downloading nonrtric-common from repo http://127.0.0.1:8879/charts
Deleting outdated charts
Successfully packaged chart and saved it to: /tmp/nonrtricgateway-1.0.0.tgz
No requirements found in /media/yev/UUI/Oran/dep/smo/bin/smo-deploy/smo-dep/nonrtric/helm/nonrtric/charts.
Error: unknown flag: --force-update
Finished Packaging NONRTRIC components [controlpanel a1controller a1simulator policymanagementservice enrichmentservice rappcatalogueservice nonrtricgateway]

...

Downloading nonrtric-common from repo http://127.0.0.1:8879/charts
Deleting outdated charts
Successfully packaged chart and saved it to: /tmp/nonrtricgateway-1.0.0.tgz
No requirements found in /media/yev/UUI/Oran/dep/smo/bin/smo-deploy/smo-dep/nonrtric/helm/nonrtric/charts.
Error: unknown flag: --force-update
Finished Packaging NONRTRIC components [controlpanel a1controller a1simulator policymanagementservice enrichmentservice rappcatalogueservice nonrtricgateway]
namespace/nonrtric created
configmap/nonrtric-recipe created
Deploying NONRTRIC
helm install -f /media/yev/UUI/Oran/dep/smo/bin/smo-deploy/smo-dep/RECIPE_EXAMPLE/NONRTRIC/example_recipe.yaml --namespace nonrtric --name r2-dev-nonrtric /media/yev/UUI/Oran/dep/smo/bin/smo-deploy/smo-dep/bin/../nonrtric/helm/nonrtric
Error: release r2-dev-nonrtric failed: no objects visited
======> Waiting for NONRTRIC to reach operatoinal state

example_recipe.yaml and

When trying to run the last line manually this is what i get:

yev@yev:/media/yev/UUI/Oran/dep/smo/bin/smo-deploy/smo-dep/RECIPE_EXAMPLE/NONRTRIC$ sudo helm install -f /media/yev/UUI/Oran/dep/smo/bin/smo-deploy/smo-dep/RECIPE_EXAMPLE/NONRTRIC/example_recipe.yaml --namespace nonrtric --name r2-dev-nonrtric /media/yev/UUI/Oran/dep/smo/bin/smo-deploy/smo-dep/bin/../nonrtric/helm/nonrtric
Error: a release named r2-dev-nonrtric already exists.
Run: helm ls --all r2-dev-nonrtric; to check the status of the release
Or run: helm del --purge r2-dev-nonrtric; to delete it
yev@yev:/media/yev/UUI/Oran/dep/smo/bin/smo-deploy/smo-dep/RECIPE_EXAMPLE/NONRTRIC$ sudo helm ls --all r2-dev-nonrtric
NAME           	REVISION	UPDATED                 	STATUS	CHART         	APP VERSION	NAMESPACE
r2-dev-nonrtric	1       	Wed Jun  9 15:43:42 2021	FAILED	nonrtric-2.0.0	           	nonrtric

purging and restarting again doesnt help

I made a folder in /media/yev/UUI/Oran/dep/smo/bin/smo-deploy/smo-dep/nonrtric/helm/nonrtric called charts and copied Chart.yaml and values.yaml from nonrtric into it. Then i tried running the install script and i got:

======> Deploying ONAP-lite

fetching local/onap

Error: chart "onap" matching version "" not found in local index. (try 'helm repo update'). no chart name found

mv: cannot stat '/home/yev/.helm/plugins/deploy/cache/onap/charts/*': No such file or directory

mv: cannot stat '/home/yev/.helm/plugins/deploy/cache/onap-subcharts/common': No such file or directory

rm: cannot remove '/home/yev/.helm/plugins/deploy/cache/onap/requirements.lock': No such file or directory

mv: cannot stat '/home/yev/.helm/plugins/deploy/cache/onap/requirements.yaml': No such file or directory

Error: no Chart.yaml exists in directory "/home/yev/.helm/plugins/deploy/cache/onap"

release "dev" deployed

So I had to run sudo make all in /media/yev/UUI/Oran/dep/smo/bin/smo-deploy/smo-oom/kubernetes

and I made sure that my copied charts do exist afterwards. Then I ran the install script again and I saw a different error:

Successfully packaged chart and saved it to: /tmp/nonrtricgateway-1.0.0.tgz
Error: error unpacking values.yaml in nonrtric: chart metadata (Chart.yaml) missing
Error: unknown flag: --force-update
Finished Packaging NONRTRIC components [controlpanel a1controller a1simulator policymanagementservice enrichmentservice rappcatalogueservice nonrtricgateway]
namespace/nonrtric created
configmap/nonrtric-recipe created
Deploying NONRTRIC
helm install -f /media/yev/UUI/Oran/dep/smo/bin/smo-deploy/smo-dep/RECIPE_EXAMPLE/NONRTRIC/example_recipe.yaml --namespace nonrtric --name r2-dev-nonrtric /media/yev/UUI/Oran/dep/smo/bin/smo-deploy/smo-dep/bin/../nonrtric/helm/nonrtric
Error: error unpacking Chart.yaml in nonrtric: chart metadata (Chart.yaml) missing

Chart.yaml::

apiVersion: v1
description: NonRealTime RAN Intelligent Controller
name: nonrtric
version: 2.0.0

dependencies:
  - name: a1controller
    version: ~2.0.0
    repository: "@local"
    condition: nonrtric.installA1controller

#here are the other dependecies which all follow the same pattern except

  - name: nonrtric-common
    version: ^2.0.0# which uses ^ instead of ~ here
    repository: "@local"
    condition: true


Could anyone please help?

Hi Experts,

I faced some issues, ricaux bronzeinfra kong is cant be Running

ricaux bronze-infra-kong-68657d8dfd-285kf 0/2 ImagePullBackOff 0 11s

ricaux deployment-ricaux-ves-65db844758-zwp8f 1/1 Running 0 17m

the logs says:

Error from server (BadRequest): a container name must be specified for pod bronze-infra-kong-68657d8dfd-285kf, choose one of: [ingress-controller proxy]

i have tried to check it out  using

kubectl logs -n ricaux bronze-infra-kong-68657d8dfd-285kf -c ingress-controller

and it says

Error from server (BadRequest): container "ingress-controller" in pod "bronze-infra-kong-68657d8dfd-285kf" is waiting to start: trying and failing to pull image

Could anyone please help?

Br,

Junior

Hi Team,

One of the deployment is not successful and also some pods are not coming up .. Kindly feedback us

NAME REVISION UPDATED STATUS CHART APP VERSION NAMESPACE
cherry-infra 1 Fri Jun 18 23:01:28 2021 DEPLOYED infrastructure-3.0.0 1.0 ricaux
cherry-ves 1 Fri Jun 18 23:03:00 2021 DEPLOYED ves-1.1.1 1.0 ricaux
dev 1 Fri Jun 18 22:02:05 2021 DEPLOYED onap-6.0.0 El Alto onap
dev-consul 1 Fri Jun 18 22:02:06 2021 DEPLOYED consul-6.0.0 onap
dev-dmaap 1 Fri Jun 18 22:02:07 2021 DEPLOYED dmaap-6.0.0 onap
dev-mariadb-galera 1 Fri Jun 18 22:02:09 2021 DEPLOYED mariadb-galera-6.0.0 onap
dev-msb 1 Fri Jun 18 22:02:11 2021 DEPLOYED msb-6.0.0 onap
dev-sdnc 1 Fri Jun 18 22:02:13 2021 FAILED sdnc-6.0.0 onap
r2-dev-nonrtric 1 Fri Jun 18 22:54:37 2021 DEPLOYED nonrtric-2.0.0 nonrtric
root@ubuntu:~# kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-5d4dd4b4db-fbj8d 1/1 Running 2 12d
kube-system coredns-5d4dd4b4db-mwrld 1/1 Running 2 12d
kube-system etcd-ubuntu 1/1 Running 4 12d
kube-system kube-apiserver-ubuntu 1/1 Running 3 12d
kube-system kube-controller-manager-ubuntu 1/1 Running 2 12d
kube-system kube-flannel-ds-rpqjt 1/1 Running 2 12d
kube-system kube-proxy-dnkbw 1/1 Running 2 12d
kube-system kube-scheduler-ubuntu 1/1 Running 2 12d
kube-system tiller-deploy-7c54c6988b-x4tkm 1/1 Running 2 12d
nonrtric a1-sim-osc-0 1/1 Running 0 11d
nonrtric a1-sim-osc-1 1/1 Running 0 8d
nonrtric a1-sim-std-0 1/1 Running 0 11d
nonrtric a1-sim-std-1 1/1 Running 0 8d
nonrtric a1controller-64c4f59fb5-dbt4q 1/1 Running 0 11d
nonrtric controlpanel-5ff4849bf-fp5bm 1/1 Running 0 11d
nonrtric db-549ff9b4d5-rqbjp 1/1 Running 1 11d
nonrtric enrichmentservice-8578855744-hqxww 1/1 Running 0 11d
nonrtric policymanagementservice-77c59f6cfb-lwrzw 1/1 Running 0 11d
nonrtric rappcatalogueservice-5945c4d84b-2z875 1/1 Running 0 11d
onap dev-consul-68d576d55c-wdnz6 1/1 Running 1 11d
onap dev-consul-server-0 1/1 Running 1 11d
onap dev-consul-server-1 1/1 Running 1 11d
onap dev-consul-server-2 1/1 Running 1 11d
onap dev-kube2msb-9b5dd678d-7hcg8 1/1 Running 0 5d
onap dev-mariadb-galera-0 0/1 Init:CrashLoopBackOff 1391 4d22h
onap dev-message-router-0 0/1 Init:0/1 119 20h
onap dev-message-router-kafka-0 1/1 Running 0 4d21h
onap dev-message-router-kafka-1 1/1 Running 0 4d21h
onap dev-message-router-kafka-2 1/1 Running 0 4d21h
onap dev-message-router-zookeeper-0 1/1 Running 0 4d22h
onap dev-message-router-zookeeper-1 1/1 Running 0 4d22h
onap dev-message-router-zookeeper-2 1/1 Running 0 4d22h
onap dev-msb-consul-65b9697c8b-zdktr 1/1 Running 1 11d
onap dev-msb-discovery-5db774ff9b-mkqnw 2/2 Running 0 5d
onap dev-msb-eag-5b94b8d7d9-tptkf 2/2 Running 0 5d
onap dev-msb-iag-79fd98f784-9rhcx 2/2 Running 0 4d23h
onap dev-sdnc-0 0/2 Init:1/3 696 4d21h
onap dev-sdnc-db-0 0/1 Init:CrashLoopBackOff 1380 4d21h
onap dev-sdnc-dmaap-listener-57977f7b9-n6mvr 0/1 Init:1/2 696 4d21h
onap dev-sdnc-dmaap-listener-5c77848759-8fbmb 0/1 Init:1/2 694 4d21h
onap dev-sdnc-sdnrdb-init-job-5xjfv 0/1 Init:Error 0 11d
onap dev-sdnc-sdnrdb-init-job-7z86s 0/1 ImagePullBackOff 0 4d21h
onap dev-sdnrdb-coordinating-only-9b9956fc-dglbh 2/2 Running 2 11d
onap dev-sdnrdb-master-0 1/1 Running 1 11d
onap dev-sdnrdb-master-1 1/1 Running 1 11d
onap dev-sdnrdb-master-2 1/1 Running 1 11d
ricaux cherry-infra-kong-7d6555954f-b56v2 2/2 Running 23 11d
ricaux deployment-ricaux-ves-6c8db5db65-kfltw 1/1 Running 0 11d
 

Hi Team,

The a1-sim-std2-0 in nonrtric namespace is not coming up.

The logs presents this message:

Version folder for simulator: STD_2.0.0
APIPATH set to: /usr/src/app/api/STD_2.0.0
PYTHONPATH set to: /usr/src/app/src/common
src/start.sh: line 38: cd: STD_2.0.0: No such file or directory
Path to callBack.py: /usr/src/app/src
Path to main.py: /usr/src/app/src
python: can't open file 'main.py': [Errno 2] No such file or directory
python: can't open file 'callBack.py': [Errno 2] No such file or directory
root@ip-172-31-36-165:~# kubectl get nos
error: the server doesn't have a resource type "nos"

This pod is using the image "nexus3.o-ran-sc.org:10002/o-ran-sc/a1-simulator:2.0.0". Below the pod describe:

Name:           a1-sim-std2-0
Namespace:      nonrtric
Priority:       0
Node:           ip-172-31-36-165/172.31.36.165
Start Time:     Tue, 29 Jun 2021 15:21:19 +0000
Labels:         app=nonrtric-a1simulator
                controller-revision-hash=a1-sim-std2-6bd765b6fc
                release=r2-dev-nonrtric
                statefulset.kubernetes.io/pod-name=a1-sim-std2-0
Annotations:    <none>
Status:         Running
IP:             10.244.0.41
Controlled By:  StatefulSet/a1-sim-std2
Containers:
  container-nonrtric-a1simulator:
    Container ID:   docker://a92c27cfc80e1b1ad07679d28c2ad1f7955613247bded80653f45ba780f37eed
    Image:          nexus3.o-ran-sc.org:10002/o-ran-sc/a1-simulator:2.0.0
    Image ID:       docker-pullable://nexus3.o-ran-sc.org:10002/o-ran-sc/a1-simulator@sha256:23efade4c7811a44d6e9762545ad9498680efca95d3c8e2321cb694c4fb719a9
    Ports:          8085/TCP, 8185/TCP
    Host Ports:     0/TCP, 0/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    2
      Started:      Wed, 30 Jun 2021 08:48:45 +0000
      Finished:     Wed, 30 Jun 2021 08:48:45 +0000
    Ready:          False
    Restart Count:  200
    Liveness:       tcp-socket :8085 delay=20s timeout=1s period=10s #success=1 #failure=3
    Readiness:      tcp-socket :8085 delay=20s timeout=1s period=10s #success=1 #failure=3
    Environment:
      A1_VERSION:  STD_2.0.0
      ALLOW_HTTP:  true
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-t96nt (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  default-token-t96nt:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-t96nt
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason   Age                     From                       Message
  ----     ------   ----                    ----                       -------
  Warning  BackOff  2m26s (x4745 over 16h)  kubelet, ip-172-31-36-165  Back-off restarting failed container

Please could anyone help here?

Regards.

Hello Experts,

  After running "./install initlocalrepo" there are 9 "kube-system" pods runnings, 26 "onap" pods running, 1 "onap" job completed, 3 "onap" jobs "Init:Error".  Not sure if the error jobs matter, since there is 1 completed job?

  In any case there are none of any other pods.  The console output shows the following:

...

Packaging NONRTRIC component [nonrtricgateway]
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "local" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
Saving 1 charts
Downloading nonrtric-common from repo http://127.0.0.1:8879/charts
Deleting outdated charts
Successfully packaged chart and saved it to: /tmp/nonrtricgateway-1.0.0.tgz
No requirements found in /root/dep/smo/bin/smo-deploy/smo-dep/nonrtric/helm/nonrtric/charts.
Error: unknown flag: --force-update
Finished Packaging NONRTRIC components [controlpanel a1controller a1simulator policymanagementservice enrichmentservice rappcatalogueservice nonrtricgateway]
Chart name-
namespace/nonrtric created
Install Kong- false
configmap/nonrtric-recipe created
Deploying NONRTRIC
helm install -f /root/dep/smo/bin/smo-deploy/smo-dep/RECIPE_EXAMPLE/NONRTRIC/example_recipe.yaml --namespace nonrtric --name r3-dev-nonrtric /root/dep/smo/bin/smo-deploy/smo-dep/bin/../nonrtric/helm/nonrtric
Error: render error in "nonrtric/templates/pv2.yaml": template: nonrtric/templates/pv2.yaml:23:16: executing "nonrtric/templates/pv2.yaml" at <include "common.namespace.nonrtric" .>: error calling include: template: no template "common.namespace.nonrtric" associated with template "gotpl"
======> Waiting for NONRTRIC to reach operatoinal state
No resources found.
No resources found.
No resources found.
No resources found.
No resources found.
0/1 A1Controller pods, 0/1 ControlPanel pods,
0/1 DB pods, 0/1 PolicyManagementService pods,
and 0/4 A1Sim pods running
No resources found.
No resources found.
No resources found.
No resources found.
No resources found.

...

This waiting just loops forever.  Please advise.  Thank you

There is actually a requirements.yaml file.  So what do the differences really mean? Here is the contents:

dependencies:
- name: a1controller
version: ~2.0.0
repository: "@local"
- name: a1simulator
version: ~2.0.0
repository: "@local"
- name: controlpanel
version: ~2.0.0
repository: "@local"
- name: policymanagementservice
version: ~2.0.0
repository: "@local"
- name: nonrtric-common
version: ^2.0.0
repository: "@local"

I'm facing the same error than Junior Salemand Deepak Duttwith pod "cherry-infra-kong" trying to install Cherry release

Error from server (BadRequest): container "ingress-controller" in pod "cherry-infra-kong-7d6555954f-thh7j" is waiting to start: trying and failing to pull image

Did someone already solved this issue? 

Hello everyone i have a problem:

++ eval 'kubectl get pods -n kube-system | grep "Running" | wc -l'
+++ kubectl get pods -n kube-system
+++ grep Running
+++ wc -l
The connection to the server localhost:8080 was refused - did you specify the right host or port?
+ NUMPODS=0
+ echo '> waiting for 0/8 pods running in namespace [kube-system] with keyword [Running]'
> waiting for 0/8 pods running in namespace [kube-system] with keyword [Running]
+ '[' 0 -lt 8 ']'
+ sleep 5

this thing happened after i do this steps from comment:

After Step 1 and Before Step #2 Change the following files

dep/tools/k8s/etc/infra.rc

dep/tools/k8s/heat/scripts/k8s_vm_install.sh

dep/smo/bin/install

if anyone have solution it will be very helpful for me

Thanks

Hi, 
im wondering, should SMO and NR-RIC should be on separate VMs or it doesn't matter (or AUX VM is dedicated for that)?

apologizes for such a basic question.

Hi all,

I have deployed SMO for the first time, the process was going well for quite a time, but suddenly got stuck in the step below, showing no action and no error.

[onap]
make[1]: Entering directory '/root/dep/smo/bin/smo-deploy/smo-oom/kubernetes'
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "local" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
Saving 34 charts
Downloading aaf from repo http://127.0.0.1:8879
Downloading aai from repo http://127.0.0.1:8879
Downloading appc from repo http://127.0.0.1:8879
Downloading cassandra from repo http://127.0.0.1:8879
Downloading cds from repo http://127.0.0.1:8879
Downloading clamp from repo http://127.0.0.1:8879
Downloading cli from repo http://127.0.0.1:8879
Downloading common from repo http://127.0.0.1:8879
Downloading consul from repo http://127.0.0.1:8879
Downloading contrib from repo http://127.0.0.1:8879
Downloading dcaegen2 from repo http://127.0.0.1:8879
Downloading dcaemod from repo http://127.0.0.1:8879
Downloading dmaap from repo http://127.0.0.1:8879
Downloading esr from repo http://127.0.0.1:8879
Downloading log from repo http://127.0.0.1:8879
Downloading sniro-emulator from repo http://127.0.0.1:8879
Downloading mariadb-galera from repo http://127.0.0.1:8879
Downloading msb from repo http://127.0.0.1:8879
Downloading multicloud from repo http://127.0.0.1:8879
Downloading nbi from repo http://127.0.0.1:8879
Downloading pnda from repo http://127.0.0.1:8879
Downloading policy from repo http://127.0.0.1:8879
Downloading pomba from repo http://127.0.0.1:8879
Downloading portal from repo http://127.0.0.1:8879
Downloading oof from repo http://127.0.0.1:8879
Downloading robot from repo http://127.0.0.1:8879
Downloading sdc from repo http://127.0.0.1:8879
Downloading sdnc from repo http://127.0.0.1:8879
Downloading so from repo http://127.0.0.1:8879
Downloading uui from repo http://127.0.0.1:8879
Downloading vfc from repo http://127.0.0.1:8879
Downloading vid from repo http://127.0.0.1:8879
Downloading vnfsdk from repo http://127.0.0.1:8879
Downloading modeling from repo http://127.0.0.1:8879
Deleting outdated charts

And nothing is happening here. What could  be the problem?

Thanks

Hi,

Does anyone know CNI configuration which is required for this exercise as my kubelet services are not started probably ? Any help is much appreciated thanks.

$ ./k8s-1node-cloud-init-k_1_15-h_2_16-d_18_09.sh

[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.

Unfortunately, an error has occurred:
timed out waiting for the condition

This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'

Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.
Here is one example how you may list all Kubernetes containers running in docker:
- 'docker ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'docker logs CONTAINERID'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher

$ systemctl status kubelet

kubelet.service - kubelet: The Kubernetes Node Agent
Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/kubelet.service.d
└─10-kubeadm.conf
Active: active (running) since Tue 2021-08-24 01:10:22 EDT; 2h 29min ago
Docs: https://kubernetes.io/docs/home/
Main PID: 10034 (kubelet)
Tasks: 21 (limit: 1112)
CGroup: /system.slice/kubelet.service
└─10034 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --cgroup

Aug 24 03:39:36 aaronchu-ubuntu1804-libvirt2 kubelet[10034]: E0824 03:39:36.824206 10034 kubelet.go:2187] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNo
Aug 24 03:39:40 aaronchu-ubuntu1804-libvirt2 kubelet[10034]: W0824 03:39:40.667054 10034 cni.go:237] Unable to update cni config: no networks found in /etc/cni/net.d
Aug 24 03:39:41 aaronchu-ubuntu1804-libvirt2 kubelet[10034]: E0824 03:39:41.838700 10034 kubelet.go:2187] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNo
Aug 24 03:39:42 aaronchu-ubuntu1804-libvirt2 kubelet[10034]: E0824 03:39:42.096513 10034 dns.go:135] Nameserver limits were exceeded, some nameservers have been omitted, the applied na
Aug 24 03:39:45 aaronchu-ubuntu1804-libvirt2 kubelet[10034]: W0824 03:39:45.667522 10034 cni.go:237] Unable to update cni config: no networks found in /etc/cni/net.d

Hi all,

One of the pods is not running.

--------------

ricaux bronze-infra-kong-68657d8dfd-4n54w 1/2 ImagePullBackOff 3 46h

ricaux deployment-ricaux-ves-65db844758-p2rhp 1/1 Running 2 46h

------------

I tried the kubectl describe pod and it shows the following:

--------------

Events:
Type                 Reason                      Age                                     From Message
---- ------ ---- ---- -------
Normal             BackOff                   19m (x257 over 78m)    kubelet, mhz-virtualbox Back-off pulling image "kong-docker-kubernetes-ingress-controller.bintray.io/kong-ingress-controller:0.7.0"
Warning            Unhealthy              14m                                     kubelet, mhz-virtualbox Liveness probe failed: Get http://10.244.0.114:9542/status: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Warning            Failed                      8m47s (x290 over 78m) kubelet, mhz-virtualbox Error: ImagePullBackOff
Normal              SandboxChanged 80s                                      kubelet, mhz-virtualbox Pod sandbox changed, it will be killed and re-created.
Normal               Created                 72s                                       kubelet, mhz-virtualbox Created container proxy
Normal                Pulled                   72s                                       kubelet, mhz-virtualbox Container image "kong:1.4" already present on machine
Normal               Started                   68s                                      kubelet, mhz-virtualbox Started container proxy
Warning              Unhealthy             58s                                      kubelet, mhz-virtualbox Readiness probe failed: Get http://10.244.0.137:9542/status: dial tcp 10.244.0.137:9542: connect: connection refused
Warning              Unhealthy             54s                                      kubelet, mhz-virtualbox Liveness probe failed: Get http://10.244.0.137:9542/status: dial tcp 10.244.0.137:9542: connect: connection refused
Warning              Unhealthy             43s                                      kubelet, mhz-virtualbox Readiness probe failed: Get http://10.244.0.137:9542/status: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Warning              Failed                     18s (x3 over 72s)             kubelet, mhz-virtualbox Error: ErrImagePull
Warning              Failed                     18s (x3 over 72s)             kubelet, mhz-virtualbox Failed to pull image "kong-docker-kubernetes-ingress-controller.bintray.io/kong-ingress-controller:0.7.0": rpc error: code = Unknown desc = Error response from daemon: error parsing HTTP 403 response body: invalid character '<' looking for beginning of value: "<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"

How do you think I can troubleshoot the ImagePullBackOff image?

Thank you

Hi,

To install SMO cherry release we make use of the below command

git clone http://gerrit.o-ran-sc.org/r/it/dep -b cherry

Similarly, to install SMO dawn release I tried the below command

git clone http://gerrit.o-ran-sc.org/r/it/dep -b dawn

This gave an error as follows,
Cloning into 'dep'...
fatal: Remote branch dawn not found in upstream origin

When I checked in their gerrit page (https://gerrit.o-ran-sc.org/r/admin/repos/it/dep,branches), 
dawn release was not available

How dawn release of SMO can be installed?

Is there any other repository for the installation?

Thank you

I am a new comer. After ran,

./k8s-1node-cloud-init-k_1_15-h_2_16-d_18_09.sh

I have noticed that the script seems not trying to install docker. By the time it needs docker, the system throws error. Could somebody tell me if I need to manually install docker beforehand?

Thanks,

Harry  

Hi Aleksey,

Yes, you are right. It seems the docker version caused the docker not installed. After leave it blank, docker is installed, but the Kubernetes seems not create a networking container such as flannel so that the coredns containers failed to come up and Kubernetes only launched 7 containers instead of 8.

Regards,

Harry

Hi Aleksey,

The Flannel failed to launch is because my local firewall blocked the connection. Thank you for your help.

Regards,

Harry

Hi Everybody,

I am installing bronze. It stuck at,

0/1 A1Controller pods, 1/1 ControlPanel pods,
1/1 DB pods, 1/1 PolicyManagementService pods,
and 0/4 A1Sim pods running

Could anybody please help?

Thanks,

Dear all,
i'm looking for solution to change default routes for Control Panel.

in my case, control panel try to use remote address (vpn) instead of VM/Container address.

"Http failure response for http://10.254.185.67:30091/a1-policy/v2/policy-types: 502 Bad Gateway"

→ i guess that there should be one of this ip
root@smo:~/dep/bin# kubectl get services -n ricaux
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
cherry-infra-kong-proxy NodePort 10.108.153.144 <none> 80:32080/TCP,443:32443/TCP 2d22h
ric-entry                          ClusterIP  10.102.52.174   <none> 80/TCP,443/TCP 2d22h
service-ricaux-ves-http   ClusterIP  10.98.92.60       <none> 8080/TCP,8443/TCP 2d22h

Hi,

 I am trying to install smo on VM with ubuntu 18.04.6 & 4 CPU:-

As per the comment of Javi G and Chirag Gandhi , I have updated my k8s...file to have:-

INFRA_DOCKER_VERSION=""
INFRA_K8S_VERSION="1.15.9"
INFRA_CNI_VERSION="0.7.5"
INFRA_HELM_VERSION="2.17.0"

But while running the command "./k8s..."

Up to 7/8 pods completed starting from 0.

Error:-

+wget https://storage.googleapis.com/kubernetes-helm/helm-v2.17.0-linux-amd64.tar.gz

Resolving storage.google.apis.com 

Connecting to storage.googleapis.com

HTTP request sent, awaiting response ... 403 Forbidden

+cd /root

+rm -rf Helm 

+mkdir Helm

+cd Helm

tar:  ../helm-v2.17.0-linux-amd64.tar.gz: Cannot Open: No such file or directory

tar: Error is not recoverable: exiting now

.

.

.

Failed to fetch https://kubernetes-charts.storage.googleapis.com/index.yaml : 403 Forbidden

I am new to this platform. I request you kindly suggest to me a fix for these issues.

Hii guys,

In step 3 I get this error.....

+ kubectl get pods --all-namespaces

The connection to the server localhost:8080 was refused - did you specify the right host or port?+ kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.ymlunable to recognize "https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp 127.0.0.1:8080: connect: connection refusedunable to recognize "https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp 127.0.0.1:8080: connect: connection refusedunable to recognize "https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp 127.0.0.1:8080: connect: connection refusedunable to recognize "https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp 127.0.0.1:8080: connect: connection refusedunable to recognize "https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp 127.0.0.1:8080: connect: connection refusedunable to recognize "https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml": Get http://localhost:8080/api?timeout=32s: dial tcp 127.0.0.1:8080: connect: connection refused+ wait_for_pods_running 8 kube-system+ NS=kube-system+ CMD='kubectl get pods --all-namespaces '+ '[' kube-system '!=' all-namespaces ']'+ CMD='kubectl get pods -n kube-system '+ KEYWORD=Running+ '[' 2 == 3 ']'+ CMD2='kubectl get pods -n kube-system | grep "Running" | wc -l'++ eval 'kubectl get pods -n kube-system | grep "Running" | wc -l'+++ kubectl get pods -n kube-system+++ grep Running+++ wc -lThe connect

This part below keeps looping continuosly

The connection to the server localhost:8080 was refused - did you specify the right host or port?
+ NUMPODS=0
+ echo '> waiting for 0/8 pods running in namespace [kube-system] with keyword [Running]'
> waiting for 0/8 pods running in namespace [kube-system] with keyword [Running]
+ '[' 0 -lt 8 ']'
+ sleep 5
++ eval 'kubectl get pods -n kube-system | grep "Running" | wc -l'
+++ kubectl get pods -n kube-system
+++ grep Running
+++ wc -l

Any ideas...I have tried editing the infra.rc file based on comments but it isnt working

Hello.

I am trying to make the SMO installation in a virtual machine but I cannot do because it appears the following message: "Unsupported kubernetes version required".

I installed kubernetes1.17.2 and uninstall kubernetes1.23.4, but it reinstalled 1.23.4 and I could not finish the k8s script. Do you know why? Thank you (I installed helm2.17.0)

Hello,

I am almost finishing the SMO Installation, but I am facing up with this problem. Can somebody figure it out?

root@oran-smo:~/dep/smo/bin# ./install
===> Starting at Fri Mar 4 11:42:18 UTC 2022

===> Cleaning up any previous deployment
======> Deleting all Helm deployments
Error: command 'delete' requires a release name
======> Clearing out all ONAP deployment resources
Error from server (NotFound): namespaces "onap" not found
No resources found
error: resource(s) were provided, but no name, label selector, or --all flag specified
error: resource(s) were provided, but no name, label selector, or --all flag specified
======> Clearing out all RICAUX deployment resources
Error from server (NotFound): namespaces "ricaux" not found
Error from server (NotFound): namespaces "ricinfra" not found
======> Clearing out all NONRTRIC deployment resources
Error from server (NotFound): namespaces "nonrtric" not found
======> Preparing for redeployment
node/oran-smo not labeled
node/oran-smo not labeled
node/oran-smo not labeled
======> Preparing working directory

===> Deploying OAM (ONAP Lite)
======> Deploying ONAP-lite
fetching local/onap
release "dev" deployed
release "dev-consul" deployed
release "dev-dmaap" deployed
release "dev-mariadb-galera" deployed
release "dev-msb" deployed
release "dev-sdnc" deployed
======> Waiting for ONAP-lite to reach operatoinal state
0/7 SDNC-SDNR pods and 0/7 Message Router pods running
0/7 SDNC-SDNR pods and 0/7 Message Router pods running
0/7 SDNC-SDNR pods and 0/7 Message Router pods running

Hello,

Can anyone point me the guidance of how to deploy SMO in E-release? This page seems outdated.

Thanks.

Hi experts, 

I am trying out the SMO installation and I am running into possibly an infinite loop in step 3.

I must mention that I separately installed docker and left it blank in the infra.rc file since I was getting the ,

"The connection to the server localhost:8080 was refused - did you specify the right host or port?"
error. 
However, I was able to pass that by doing the above but I am stuck after only 5/8 pods.

+ NUMPODS=5
+ echo '> waiting for 5/8 pods running in namespace [kube-system] with keyword [Running]'
> waiting for 5/8 pods running in namespace [kube-system] with keyword [Running]
+ '[' 5 -lt 8 ']'
+ sleep 5

This is displayed for a very long time now. Any help to overcome this issue will be highly appreciated.

You need to install specific version of docker before starting smo installation. follow instructions in Install Docker Engine on Ubuntu | Docker Documentation.

Hi All ,

          I am trying to install cherry release of SMO.I managed to successfully complete first 3 steps of installation. I am having below issue with 4th step. step remains in loop forever. I have checked the output for POD state in onap name space. Some pods remain init state and some frequently crash. Find below out put pod state. Can anyone guide on how to resolve below issue?

NAME READY STATUS RESTARTS AGE
dev-consul-68d576d55c-qspwq 1/1 Running 0 8h
dev-consul-server-0 1/1 Running 0 8h
dev-consul-server-1 1/1 Running 0 8h
dev-consul-server-2 1/1 Running 0 8h
dev-kube2msb-9b5dd678d-f5fg9 0/1 CrashLoopBackOff 95 8h
dev-mariadb-galera-0 0/1 CrashLoopBackOff 123 8h
dev-message-router-0 0/1 Init:0/1 48 8h
dev-message-router-kafka-0 0/1 CrashLoopBackOff 87 8h
dev-message-router-kafka-1 0/1 CrashLoopBackOff 87 8h
dev-message-router-kafka-2 0/1 CrashLoopBackOff 87 8h
dev-message-router-zookeeper-0 1/1 Running 0 8h
dev-message-router-zookeeper-1 1/1 Running 0 8h
dev-message-router-zookeeper-2 1/1 Running 0 8h
dev-msb-consul-77f4d5fd44-qfp8r 1/1 Running 0 8h
dev-msb-discovery-5db774ff9b-pslg7 2/2 Running 0 8h
dev-msb-eag-5b94b8d7d9-tlvvj 2/2 Running 0 8h
dev-msb-iag-79fd98f784-qnc8d 2/2 Running 0 8h
dev-sdnc-0 2/2 Running 0 8h
dev-sdnc-db-0 0/1 Running 127 8h
dev-sdnc-dmaap-listener-57977f7b9-62szx 0/1 Init:1/2 48 8h
dev-sdnc-sdnrdb-init-job-vk8m8 0/1 Completed 0 8h
dev-sdnrdb-coordinating-only-587798dccf-l652l 2/2 Running 0 8h
dev-sdnrdb-master-0 1/1 Running 0 8h
dev-sdnrdb-master-1 1/1 Running 0 8h
dev-sdnrdb-master-2 1/1 Running 0 8h

Kubectl describe details for dev-mariadb-Galera-0

kubectl describe pods dev-mariadb-galera-0 -n onap
Name: dev-mariadb-galera-0
Namespace: onap
Priority: 0
Node: oran-smo/172.20.0.4
Start Time: Wed, 17 Aug 2022 19:35:30 +0000
Labels: app=dev-mariadb-galera
chart=mariadb-galera-6.0.0
controller-revision-hash=dev-mariadb-galera-7b9574778c
heritage=Tiller
release=dev
statefulset.kubernetes.io/pod-name=dev-mariadb-galera-0
Annotations: pod.alpha.kubernetes.io/initialized: true
Status: Running
IP: 10.244.0.237
Controlled By: StatefulSet/dev-mariadb-galera
Init Containers:
mariadb-galera-prepare:
Container ID: docker://ab472c0d8ee7479f36d7b22bfdcee717d8b4b225557bab5b2c8fbbdc02c3593d
Image: nexus3.onap.org:10001/busybox
Image ID: docker-pullable://busybox@sha256:ef320ff10026a50cf5f0213d35537ce0041ac1d96e9b7800bafd8bc9eff6c693
Port: <none>
Host Port: <none>
Command:
sh
-c
chown -R 27:27 /var/lib/mysql
State: Terminated
Reason: Completed
Exit Code: 0
Started: Wed, 17 Aug 2022 19:35:56 +0000
Finished: Wed, 17 Aug 2022 19:35:56 +0000
Ready: True
Restart Count: 0
Environment: <none>
Mounts:
/var/lib/mysql from dev-mariadb-galera-data (rw)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-wk42p (ro)
Containers:
mariadb-galera:
Container ID: docker://16f9b922558b30a34f2ee4700379a2b16a9945a043daa44f1d1699cf5ca9dc74
Image: nexus3.onap.org:10001/adfinissygroup/k8s-mariadb-galera-centos:v002
Image ID: docker-pullable://nexus3.onap.org:10001/adfinissygroup/k8s-mariadb-galera-centos@sha256:fbcb842f30065ae94532cb1af9bb03cc6e2acaaf896d87d0ec38da7dd09a3dde
Ports: 3306/TCP, 4444/TCP, 4567/TCP, 4568/TCP
Host Ports: 0/TCP, 0/TCP, 0/TCP, 0/TCP
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 137
Started: Thu, 18 Aug 2022 03:43:09 +0000
Finished: Thu, 18 Aug 2022 03:44:38 +0000
Ready: False
Restart Count: 125
Liveness: exec [mysqladmin ping] delay=30s timeout=5s period=10s #success=1 #failure=3
Readiness: exec [/usr/share/container-scripts/mysql/readiness-probe.sh] delay=15s timeout=5s period=10s #success=1 #failure=3
Environment:
POD_NAMESPACE: onap (v1:metadata.namespace)
MYSQL_USER: <set to the key 'login' in secret 'dev-mariadb-galera-db-user-credentials'> Optional: false
MYSQL_PASSWORD: <set to the key 'password' in secret 'dev-mariadb-galera-db-user-credentials'> Optional: false
MYSQL_DATABASE:
MYSQL_ROOT_PASSWORD: <set to the key 'password' in secret 'dev-mariadb-galera-db-root-password'> Optional: false
Mounts:
/etc/localtime from localtime (ro)
/usr/share/container-scripts/mysql/configure-mysql.sh from init-script (rw,path="configure-mysql.sh")
/var/lib/mysql from dev-mariadb-galera-data (rw)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-wk42p (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
dev-mariadb-galera-data:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: dev-mariadb-galera-data-dev-mariadb-galera-0
ReadOnly: false
init-script:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: dev-mariadb-galera
Optional: false
localtime:
Type: HostPath (bare host directory volume)
Path: /etc/localtime
HostPathType:
default-token-wk42p:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-wk42p
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Unhealthy 37m (x896 over 8h) kubelet, oran-smo Readiness probe failed: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2 "No such file or directory")
Warning Unhealthy 13m (x372 over 8h) kubelet, oran-smo Liveness probe failed: mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2 "No such file or directory")'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!
Warning BackOff 3m1s (x1529 over 8h) kubelet, oran-smo Back-off restarting failed container

kubectl describe pods dev-kube2msb-9b5dd678d-f5fg9 -n onap
Name: dev-kube2msb-9b5dd678d-f5fg9
Namespace: onap
Priority: 0
Node: oran-smo/172.20.0.4
Start Time: Wed, 17 Aug 2022 19:35:29 +0000
Labels: app=kube2msb
pod-template-hash=9b5dd678d
release=dev
Annotations: sidecar.istio.io/inject: true
Status: Running
IP: 10.244.0.227
Controlled By: ReplicaSet/dev-kube2msb-9b5dd678d
Init Containers:
kube2msb-readiness:
Container ID: docker://2ebc7f96179b882fc317dd5e2d875a7b5067e1ecb8bbcd2f3f2af66ba8278715
Image: oomk8s/readiness-check:2.2.1
Image ID: docker-pullable://oomk8s/readiness-check@sha256:dc4d07abf8d936823f1968698f3ac9b9d719e82271fd8243aa142a5f1b92a833
Port: <none>
Host Port: <none>
Command:
/root/ready.py
Args:
--container-name
msb-discovery
State: Terminated
Reason: Completed
Exit Code: 0
Started: Wed, 17 Aug 2022 19:35:48 +0000
Finished: Wed, 17 Aug 2022 19:36:36 +0000
Ready: True
Restart Count: 0
Environment:
NAMESPACE: onap (v1:metadata.namespace)
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from msb-token-6wfxl (ro)
Containers:
kube2msb:
Container ID: docker://703758cb122b4c2b466503d4f285374b08b1359ad5a2657f0fd0d6f76714f553
Image: nexus3.onap.org:10001/onap/oom/kube2msb:1.2.6
Image ID: docker-pullable://nexus3.onap.org:10001/onap/oom/kube2msb@sha256:c0f690dbe43d38a3663b1f54fabd9bf75933235b4640ed3ef8688cea4461e351
Port: <none>
Host Port: <none>
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Thu, 18 Aug 2022 03:47:25 +0000
Finished: Thu, 18 Aug 2022 03:47:40 +0000
Ready: False
Restart Count: 97
Environment:
KUBE_MASTER_URL: https://kubernetes.default:443
MSB_URL: http://msb-discovery.onap:10081
Mounts:
/etc/localtime from localtime (ro)
/var/run/secrets/kubernetes.io/serviceaccount from msb-token-6wfxl (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
localtime:
Type: HostPath (bare host directory volume)
Path: /etc/localtime
HostPathType:
msb-token-6wfxl:
Type: Secret (a volume populated by a Secret)
SecretName: msb-token-6wfxl
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Pulled 31m (x93 over 8h) kubelet, oran-smo Container image "nexus3.onap.org:10001/onap/oom/kube2msb:1.2.6" already present on machine
Warning BackOff 75s (x2189 over 8h) kubelet, oran-smo Back-off restarting failed container

Hi while doing get the same issue. 

Step 4: Installation of Kubernetes, Helm, Docker, etc.
Run ...
$ ./k8s-1node-cloud-init-k_1_16-h_2_12-d_cur.sh-

Here received like- 

Waiting for 5/8 pods running in namespace.

And only 5 pods were created and then still show running. Anyone can support for same. 

br

ajeet

Hi all appreciate and thanks to all for such nice to complete deployment process . 

I am geeting issue here related to>>>

Checking Container Health

Check the health of the application manager platform component by querying it via the ingress controller using the following command.

% curl -v http://localhost:32080/appmgr/ric/v1/health/ready

While running above command :::

* Trying 127.0.0.1:32080...
* TCP_NODELAY set
* connect to 127.0.0.1 port 32080 failed: Connection timed out
* Failed to connect to localhost port 32080: Connection timed out
* Closing connection 0
curl: (28) Failed to connect to localhost port 32080: Connection timed out
root@ip-172-31-93-71:/home/ubuntu/ric-dep/bin#


Pls suppoer as per the docs reference below- 

https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-ric-dep/en/latest/installation-guides.html


br
ajeet

Dears, I there solution?

NUMPODS=5

+ echo '> waiting for 5/8 pods running in namespace [kube-system] with keyword [Running]'

> waiting for 5/8 pods running in namespace [kube-system] with keyword [Running]

+ '[' 5 -lt 8 ']'

+ sleep 5

^Z