Re: [onap-discuss] OOM errors cannot deploy ONAP - with error logs

2018-03-03 Thread abdelmuhaimen.seaudi
Hi,

I was able to resolve this issue by changing
#pullPolicy: Always
to
pullPoicy: IfNotPresent
in
/oom/kubernetes/portal/values.yaml

and now the portal is up and running
portal-apps-78498f9c4b-rxhvf   2/2   Running0   
   7m
portal-db-8d8575f89-jgs27  1/1   Running0   
   7m
portal-vnc-744777b66-7hcr7 0/1   Init:1/4   0   
   7m
portal-widgets-68c655bddd-9wpc51/1   Running0   
   7m


From: onap-discuss-boun...@lists.onap.org [onap-discuss-boun...@lists.onap.org] 
on behalf of abdelmuhaimen.sea...@orange.com [abdelmuhaimen.sea...@orange.com]
Sent: Saturday, March 03, 2018 8:13 PM
To: Vivekanandan Muthukrishnan
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] OOM errors cannot deploy ONAP - with error logs

Hi Vivekanandan,

Thanks for your reply.

I deleted the portal-db docker image, and then i pulled it again, but the 
service still does not come up.

root@ole-k8s:~/oom/kubernetes/oneclick# ./deleteAll.bash -n onap -a portal
Current kubectl context does not match context specified: onap
You are about to delete deployment from: onap
To continue enter context name: onap

** Cleaning up ONAP:
release "onap-portal" deleted
clusterrolebinding "onap-portal-admin-binding" deleted
Service account onap-portal-admin-binding deleted.

Waiting for namespaces termination...

** Gone **

root@ole-k8s:~/oom/kubernetes/oneclick# docker rmi 
nexus3.onap.org:10001/onap/portal-db:v1.3.0
Untagged: nexus3.onap.org:10001/onap/portal-db:v1.3.0
Untagged: 
nexus3.onap.org:10001/onap/portal-db@sha256:f62c1fa3fb47d553c96a8a5e785ca389f69d8e893eed486935ff5c66d9d8683a
Deleted: sha256:7578762221a79a04b2b470656fe3d62ca5fc01ee697e099c94a2b62e19c21989
Deleted: sha256:e2bc68806e60ce373040a646c7c31bf339656f1d9c2cf2c0732d7f7710ffcfc5
Deleted: sha256:911f78ca2e0ffbd07d45ddef60b39f0bf969846de6117466ff3cee9d7140f717
Deleted: sha256:3af70a1a8a9bd5e78e87c95a32869186408af9023702f40ade7af2cca77c4337
Deleted: sha256:44769d62b4f509d4a89eb2338a44aa3008f75ddb065f5a518c869d20346b0919
Deleted: sha256:48a58d780ca2ed1d0e7fd31ba2fe864fc2ab0aa293614c212f3836d2fca81934
Deleted: sha256:e1469134b78941676be645cb31f3e115bb20390257b57e7bba1bc5132ad7e68c
Deleted: sha256:d06029fc5d41284de07b286b437631cd9497338e78bf246926b0ac7745d0eacd
Deleted: sha256:6fd8fddc3e304ed1f00b843cb5fd57102c728b71696b05e9b59fcb91c1bc6242
Deleted: sha256:cdabe75b529fc6bf52e955cdecf6522bb100438e32ff1ea28e1b5a092ba6c40a
Deleted: sha256:1abc786e737ceeaf6df2f454f79ee856ba0ca36b323557e4928e585961e6c8c6
Deleted: sha256:8b2ab5cd414d584a648ec0649b67d9a252aab6ab41f027391ebb5a5f3abaee85
Deleted: sha256:04e65b6a021b2c1dca51bd9c454ec68a599022d2eb564f2b9fcbd4a03d8b1a4d
Deleted: sha256:98b9343ade53aba000fc5cf90aed7d6a12363655a1ebbe675ea040f8320fd584
Deleted: sha256:86c0872a3ae20d67865ff9cb92f16818963cb6bf9d74ac3d1cb3f44bdb4adb52
Deleted: sha256:9e108ca098e2a8eb22b78edd5e6e53c0a2c3d4dddb3a1dd7bd5107d681800933
Deleted: sha256:0f0380d5dab3db9c5310830c983602dd9b8b29f1412827bed361c60d7b44c870
Deleted: sha256:f86a0aefab394249e80865d4bf41f761a3f44c616852b35a8fcb6a2c5532f333
Deleted: sha256:708cb5ace70a02c0ab7b7dc34256e5a45a759ef48cdfaf1e51d0401437f5688c
Deleted: sha256:fa66485ef54b61f8f2de2d81271135976794c45628d309fd361a99b53256ab44
Deleted: sha256:7ba2d138e04445addacd95ddb1c186ee9e236db0d7464c4ff63aac6e002b8dfb

root@ole-k8s:~/oom/kubernetes/oneclick# docker pull 
nexus3.onap.org:10001/onap/portal-db:v1.3.0
v1.3.0: Pulling from onap/portal-db
c20dc0c5afeb: Already exists
eaea58e86ed4: Pull complete
424e934f382c: Pull complete
d257750d0801: Pull complete
e02efc64fc93: Pull complete
7b55963ca168: Pull complete
cc422ac43a3b: Pull complete
175afe956bca: Pull complete
9931f584f413: Pull complete
52dd0882586f: Pull complete
e4eac6819242: Pull complete
f5f581ea39f6: Pull complete
e4ef92b2ee7f: Pull complete
82e7c5ae8d51: Pull complete
f4a1053fdd34: Pull complete
730577ac2b2d: Pull complete
fc768467a6e9: Pull complete
4da2b2d2f77e: Pull complete
20bd2ee92b3d: Pull complete
32f94035060a: Pull complete
07be12eb4e2e: Pull complete
Digest: sha256:f62c1fa3fb47d553c96a8a5e785ca389f69d8e893eed486935ff5c66d9d8683a
Status: Downloaded newer image for nexus3.onap.org:10001/onap/portal-db:v1.3.0

root@ole-k8s:~/oom/kubernetes/oneclick# ./createAll.bash -n onap -a portal

** Creating instance 1 of ONAP with port range 30200 and 30399

** Creating ONAP:


** Creating deployments for portal **

Creating service account **
clusterrolebinding "onap-portal-admin-binding" created

Creating deployments and services **
NAME:   onap-portal
LAST DEPLOYED: Sat Mar  3 18:06:48 2018
NAMESPACE: onap
STATUS: DEPLOYED

RESOURCES:
==> v1beta1/Deployment
NAMEDESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
portal-apps 111 

Re: [onap-discuss] OOM errors cannot deploy ONAP - with error logs

2018-03-03 Thread abdelmuhaimen.seaudi
STATUS   VOLUME  CAPACITY  ACCESSMODES  STORAGECLASS  AGE
portal-db  Pending  1s

==> v1/Service
NAME   CLUSTER-IPEXTERNAL-IP  PORT(S)   
AGE
portalwidgets  None 8082/TCP  
1s
portaldb   None 3306/TCP  
1s
portalapps 10.43.243.64
8006:30213/TCP,8010:30214/TCP,8989:30215/TCP  1s
portal-vnc 10.43.73.1486080:30211/TCP,5900:30212/TCP 
1s




 Done 

root@ole-k8s:~/oom/kubernetes/oneclick# kubectl get pods --namespace onap | 
grep portal
portal-apps-7ddfc4b6bd-f9t7t   0/2   Init:0/3   0   
   56s
portal-db-6854cd4699-c8pjk 0/1   Pending0   
   56s
portal-vnc-7dcbf79f66-tgjdp0/1   Init:0/4   0   
   56s
portal-widgets-6979b47c48-828vh0/1   Init:0/1   0   
   56s
sdnc-portal-69b79b6646-fmxh9   1/1   Running0   
   1h

root@ole-k8s:~/oom/kubernetes/oneclick# kubectl get pods --namespace onap | 
grep portal
portal-apps-7ddfc4b6bd-f9t7t   0/2   Init:0/3   0   
   2m
portal-db-6854cd4699-c8pjk 0/1   ErrImagePull   0   
   2m
portal-vnc-7dcbf79f66-tgjdp0/1   Init:0/4   0   
   2m
portal-widgets-6979b47c48-828vh0/1   Init:0/1   0   
   2m
sdnc-portal-69b79b6646-fmxh9   1/1   Running0   
   1h
root@ole-k8s:~/oom/kubernetes/oneclick#

root@ole-k8s:~/oom/kubernetes/oneclick# kubectl get pods --namespace onap | 
grep portal
portal-apps-7ddfc4b6bd-f9t7t   0/2   Init:0/3   0   
   3m
portal-db-6854cd4699-c8pjk 0/1   ImagePullBackOff   0   
   3m
portal-vnc-7dcbf79f66-tgjdp0/1   Init:0/4   0   
   3m
portal-widgets-6979b47c48-828vh0/1   Init:0/1   0   
   3m
sdnc-portal-69b79b6646-fmxh9   1/1   Running0   
   1h
root@ole-k8s:~/oom/kubernetes/oneclick#




From: Vivekanandan Muthukrishnan [vmuthukrish...@aarnanetworks.com]
Sent: Saturday, March 03, 2018 7:31 PM
To: SEAUDI Abdelmuhaimen OBS/CSO
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] OOM errors cannot deploy ONAP - with error logs

Hi Abdel,

It seems like you are having some internet connective issues and many of your 
containers are in "ImagePullBackOff" state.

Kindly check your net connection and redeploy the oom containers again.

Regards
Vivek



On Sat, Mar 3, 2018 at 10:28 PM, 
<abdelmuhaimen.sea...@orange.com<mailto:abdelmuhaimen.sea...@orange.com>> wrote:
Hi,

After trying again, using the script in the wiki

I noticed that the portal-db is in error ImagePullBackOff with 
Reason:ErrImagePull

root@ole-k8s:~/oom/kubernetes/oneclick# kubectl get pods --namespace onap | 
grep portal
portal-apps-7ddfc4b6bd-ffd5m   0/2   Init:0/3   1   
   12m
portal-db-6854cd4699-9j8hn 0/1   ImagePullBackOff   0   
   12m
portal-vnc-7dcbf79f66-4pk5g0/1   Init:0/4   1   
   12m
portal-widgets-6979b47c48-m96lq0/1   Init:0/1   1   
   12m

Events:
  Type Reason Age   From
Message
   --   
---
  Normal   Scheduled  3mdefault-scheduler   
Successfully assigned portal-db-6854cd4699-9j8hn to ole-k8s.novalocal
  Normal   SuccessfulMountVolume  3mkubelet, ole-k8s.novalocal  
MountVolume.SetUp succeeded for volume "localtime"
  Normal   SuccessfulMountVolume  3mkubelet, ole-k8s.novalocal  
MountVolume.SetUp succeeded for volume "onap-portal"
  Normal   SuccessfulMountVolume  2mkubelet, ole-k8s.novalocal  
MountVolume.SetUp succeeded for volume "default-token-dl7dn"
  Normal   SandboxChanged 2mkubelet, ole-k8s.novalocal  
Pod sandbox changed, it will be killed and re-created.
  Normal   Pulling54s (x4 over 2m)  kubelet, ole-k8s.novalocal  
pulling image 
"nexus3.onap.org:10001/onap/portal-db:v1.3.0<http://nexus3.onap.org:10001/onap/portal-db:v1.3.0>"
  Warning  Failed 53s (x4 over 2m)  kubelet, ole-k8s.novalocal  
Failed to pull image 
"nexus3.onap.org:10001/onap/portal-db:v1.3.0<http://nexus3.onap.org:10001/onap/portal-db:v1.3.0>":
 rpc error: code = Unknown desc = Error: image onap/portal-db:v1.3.0 not found
  Warning  FailedSync 21s (x8 over 2m)  kubelet, ole-k8

Re: [onap-discuss] OOM errors cannot deploy ONAP - with error logs

2018-03-03 Thread Vivekanandan Muthukrishnan
Hi Abdel,

It seems like you are having some internet connective issues and many of
your containers are in "ImagePullBackOff" state.

Kindly check your net connection and redeploy the oom containers again.

Regards
Vivek



On Sat, Mar 3, 2018 at 10:28 PM, <abdelmuhaimen.sea...@orange.com> wrote:

> Hi,
>
> After trying again, using the script in the wiki
>
> I noticed that the portal-db is in error ImagePullBackOff with
> Reason:ErrImagePull
>
> root@ole-k8s:~/oom/kubernetes/oneclick# kubectl get pods --namespace onap
> | grep portal
> portal-apps-7ddfc4b6bd-ffd5m   0/2   Init:0/3
>  1  12m
> portal-db-6854cd4699-9j8hn 0/1   ImagePullBackOff
>  0  12m
> portal-vnc-7dcbf79f66-4pk5g0/1   Init:0/4
>  1  12m
> portal-widgets-6979b47c48-m96lq0/1   Init:0/1
>1  12m
>
> Events:
>   Type Reason Age   From
>   Message
>    --   
>   ---
>   Normal   Scheduled  3mdefault-scheduler
>  Successfully assigned portal-db-6854cd4699-9j8hn to ole-k8s.novalocal
>   Normal   SuccessfulMountVolume  3mkubelet,
> ole-k8s.novalocal  MountVolume.SetUp succeeded for volume "localtime"
>   Normal   SuccessfulMountVolume  3mkubelet,
> ole-k8s.novalocal  MountVolume.SetUp succeeded for volume "onap-portal"
>   Normal   SuccessfulMountVolume  2mkubelet,
> ole-k8s.novalocal  MountVolume.SetUp succeeded for volume
> "default-token-dl7dn"
>   Normal   SandboxChanged 2mkubelet,
> ole-k8s.novalocal  Pod sandbox changed, it will be killed and re-created.
>   Normal   Pulling54s (x4 over 2m)  kubelet,
> ole-k8s.novalocal  pulling image "nexus3.onap.org:10001/onap/
> portal-db:v1.3.0"
>   Warning  Failed 53s (x4 over 2m)  kubelet,
> ole-k8s.novalocal  Failed to pull image "nexus3.onap.org:10001/onap/
> portal-db:v1.3.0": rpc error: code = Unknown desc = Error: image
> onap/portal-db:v1.3.0 not found
>   Warning  FailedSync 21s (x8 over 2m)  kubelet,
> ole-k8s.novalocal  Error syncing pod
>   Normal   BackOff21s (x4 over 2m)  kubelet,
> ole-k8s.novalocal  Back-off pulling image "nexus3.onap.org:10001/onap/
> portal-db:v1.3.0"
>
>
>
> Although, i can see that the image exists on the VM.
>
> root@ole-k8s:~/oom/kubernetes/oneclick# docker images | grep "
> nexus3.onap.org:10001/onap/portal-db"
> nexus3.onap.org:10001/onap/portal-db  v1.3.0
> 7578762221a74 months ago398 MB
>
> Any idea why the portal-db is showing this error ?
>
> Thanks
>
> Abdelmuhaimen Seaudi
> Orange Labs Egypt
> Mobile:+2012 84644 733
> ----------
> *From:* onap-discuss-boun...@lists.onap.org [onap-discuss-bounces@lists.
> onap.org] on behalf of abdelmuhaimen.sea...@orange.com [
> abdelmuhaimen.sea...@orange.com]
> *Sent:* Saturday, March 03, 2018 3:11 PM
> *To:* onap-discuss@lists.onap.org
> *Subject:* [onap-discuss] OOM errors cannot deploy ONAP - with error logs
>
> Hi,
>
> I am trying to deploy onap on an Openstack 64GB RAM VM, using the oom
> startup script from this link https://jira.onap.org/secure/
> attachment/11206/oom_entrypoint.sh
>
> Rancher comes up OK, host is registered.
>
> However, I get some errors while pulling the docker images, and some pods
> are running and rest have errors, and i cannot login to the portal.
>
> Error parsing reference: "2.0.0-SNAPSHOT" is not a valid repository/tag:
> repository name must be lowercase
> Error: image onap/vfc/ztevnfmdriver:v1.0.2 not found
> Error response from daemon: repository v1.1.0 not found: does not exist or
> no pull access
> Error: image onap/org.onap.dcaegen2.deployments.bootstrap:latest not found
> error pulling image configuration: unknown blob
> Error response from daemon: manifest for oomk8s/config-init:latest not
> found
> ERROR: /root/.ssh/onap_rsa does not exist or is empty.  Cannot launch dcae
> gen2.
> ERROR: dcaegen2 failed to configure: Pre-requisites not met.  Skipping
> deploying it and continue
>
> root@ole-k8s:~# kubectl get pods --all-namespaces -a
> NAMESPACE NAME   READY
>  STATUS RESTARTS   AGE
> kube-system   heapster-76b8cd7b5-jd96b   1/1
>  Running0  6h
> kube-system   kube-dns-5d7b4487c9-bk8fd  3/3
>  Running0   

Re: [onap-discuss] OOM errors cannot deploy ONAP - with error logs

2018-03-03 Thread abdelmuhaimen.seaudi
Hi,

After trying again, using the script in the wiki

I noticed that the portal-db is in error ImagePullBackOff with 
Reason:ErrImagePull

root@ole-k8s:~/oom/kubernetes/oneclick# kubectl get pods --namespace onap | 
grep portal
portal-apps-7ddfc4b6bd-ffd5m   0/2   Init:0/3   1   
   12m
portal-db-6854cd4699-9j8hn 0/1   ImagePullBackOff   0   
   12m
portal-vnc-7dcbf79f66-4pk5g0/1   Init:0/4   1   
   12m
portal-widgets-6979b47c48-m96lq0/1   Init:0/1   1   
   12m

Events:
  Type Reason Age   From
Message
   --   
---
  Normal   Scheduled  3mdefault-scheduler   
Successfully assigned portal-db-6854cd4699-9j8hn to ole-k8s.novalocal
  Normal   SuccessfulMountVolume  3mkubelet, ole-k8s.novalocal  
MountVolume.SetUp succeeded for volume "localtime"
  Normal   SuccessfulMountVolume  3mkubelet, ole-k8s.novalocal  
MountVolume.SetUp succeeded for volume "onap-portal"
  Normal   SuccessfulMountVolume  2mkubelet, ole-k8s.novalocal  
MountVolume.SetUp succeeded for volume "default-token-dl7dn"
  Normal   SandboxChanged 2mkubelet, ole-k8s.novalocal  
Pod sandbox changed, it will be killed and re-created.
  Normal   Pulling54s (x4 over 2m)  kubelet, ole-k8s.novalocal  
pulling image "nexus3.onap.org:10001/onap/portal-db:v1.3.0"
  Warning  Failed 53s (x4 over 2m)  kubelet, ole-k8s.novalocal  
Failed to pull image "nexus3.onap.org:10001/onap/portal-db:v1.3.0": rpc error: 
code = Unknown desc = Error: image onap/portal-db:v1.3.0 not found
  Warning  FailedSync 21s (x8 over 2m)  kubelet, ole-k8s.novalocal  
Error syncing pod
  Normal   BackOff21s (x4 over 2m)  kubelet, ole-k8s.novalocal  
Back-off pulling image "nexus3.onap.org:10001/onap/portal-db:v1.3.0"



Although, i can see that the image exists on the VM.

root@ole-k8s:~/oom/kubernetes/oneclick# docker images | grep 
"nexus3.onap.org:10001/onap/portal-db"
nexus3.onap.org:10001/onap/portal-db  v1.3.0
  7578762221a74 months ago398 MB

Any idea why the portal-db is showing this error ?

Thanks

Abdelmuhaimen Seaudi
Orange Labs Egypt
Mobile:+2012 84644 733

From: onap-discuss-boun...@lists.onap.org [onap-discuss-boun...@lists.onap.org] 
on behalf of abdelmuhaimen.sea...@orange.com [abdelmuhaimen.sea...@orange.com]
Sent: Saturday, March 03, 2018 3:11 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] OOM errors cannot deploy ONAP - with error logs

Hi,

I am trying to deploy onap on an Openstack 64GB RAM VM, using the oom startup 
script from this link 
https://jira.onap.org/secure/attachment/11206/oom_entrypoint.sh

Rancher comes up OK, host is registered.

However, I get some errors while pulling the docker images, and some pods are 
running and rest have errors, and i cannot login to the portal.

Error parsing reference: "2.0.0-SNAPSHOT" is not a valid repository/tag: 
repository name must be lowercase
Error: image onap/vfc/ztevnfmdriver:v1.0.2 not found
Error response from daemon: repository v1.1.0 not found: does not exist or no 
pull access
Error: image onap/org.onap.dcaegen2.deployments.bootstrap:latest not found
error pulling image configuration: unknown blob
Error response from daemon: manifest for oomk8s/config-init:latest not found
ERROR: /root/.ssh/onap_rsa does not exist or is empty.  Cannot launch dcae gen2.
ERROR: dcaegen2 failed to configure: Pre-requisites not met.  Skipping 
deploying it and continue

root@ole-k8s:~# kubectl get pods --all-namespaces -a
NAMESPACE NAME   READY STATUS   
  RESTARTS   AGE
kube-system   heapster-76b8cd7b5-jd96b   1/1   Running  
  0  6h
kube-system   kube-dns-5d7b4487c9-bk8fd  3/3   Running  
  0  6h
kube-system   kubernetes-dashboard-f9577fffd-trhqs   1/1   Running  
  0  6h
kube-system   monitoring-grafana-997796fcf-268xn 1/1   Running  
  0  6h
kube-system   monitoring-influxdb-56fdcd96b-gbbwz1/1   Running  
  0  6h
kube-system   tiller-deploy-cc96d4f6b-hqs6t  1/1   Running  
  0  6h
onap  aaf-6c64db8fdd-fvrcv   0/1   Init:0/1 
  33 6h
onap  aaf-cs-75464db899-jtldk0/1   
ImagePullBackOff   0  6h
onap  aai-data-router-6fbb8695d4-bdsld   0/1   
I

[onap-discuss] OOM errors cannot deploy ONAP - with error logs

2018-03-03 Thread abdelmuhaimen.seaudi
Hi,

I am trying to deploy onap on an Openstack 64GB RAM VM, using the oom startup 
script from this link 
https://jira.onap.org/secure/attachment/11206/oom_entrypoint.sh

Rancher comes up OK, host is registered.

However, I get some errors while pulling the docker images, and some pods are 
running and rest have errors, and i cannot login to the portal.

Error parsing reference: "2.0.0-SNAPSHOT" is not a valid repository/tag: 
repository name must be lowercase
Error: image onap/vfc/ztevnfmdriver:v1.0.2 not found
Error response from daemon: repository v1.1.0 not found: does not exist or no 
pull access
Error: image onap/org.onap.dcaegen2.deployments.bootstrap:latest not found
error pulling image configuration: unknown blob
Error response from daemon: manifest for oomk8s/config-init:latest not found
ERROR: /root/.ssh/onap_rsa does not exist or is empty.  Cannot launch dcae gen2.
ERROR: dcaegen2 failed to configure: Pre-requisites not met.  Skipping 
deploying it and continue

root@ole-k8s:~# kubectl get pods --all-namespaces -a
NAMESPACE NAME   READY STATUS   
  RESTARTS   AGE
kube-system   heapster-76b8cd7b5-jd96b   1/1   Running  
  0  6h
kube-system   kube-dns-5d7b4487c9-bk8fd  3/3   Running  
  0  6h
kube-system   kubernetes-dashboard-f9577fffd-trhqs   1/1   Running  
  0  6h
kube-system   monitoring-grafana-997796fcf-268xn 1/1   Running  
  0  6h
kube-system   monitoring-influxdb-56fdcd96b-gbbwz1/1   Running  
  0  6h
kube-system   tiller-deploy-cc96d4f6b-hqs6t  1/1   Running  
  0  6h
onap  aaf-6c64db8fdd-fvrcv   0/1   Init:0/1 
  33 6h
onap  aaf-cs-75464db899-jtldk0/1   
ImagePullBackOff   0  6h
onap  aai-data-router-6fbb8695d4-bdsld   0/1   
ImagePullBackOff   0  6h
onap  aai-elasticsearch-7f66545fdf-dtxbr 1/1   Running  
  0  6h
onap  aai-hbase-5bcb5884d4-gs7jg 1/1   Running  
  0  6h
onap  aai-model-loader-service-7768db4744-8hw9s  1/2   
ImagePullBackOff   0  6h
onap  aai-resources-58d4966887-4t8cg 1/2   
ImagePullBackOff   0  6h
onap  aai-search-data-service-99dff479c-twlgn1/2   
ImagePullBackOff   0  6h
onap  aai-service-5698ddc455-s25dd   0/1   Init:0/1 
  33 6h
onap  aai-sparky-be-57bd9944b5-8qb7p 1/2   
ImagePullBackOff   0  6h
onap  aai-traversal-557f8fc78d-mpp8f 0/2   Init:0/1 
  1  6h
onap  appc-67c6b9d477-sv97q  1/2   
ErrImagePull   0  6h
onap  appc-dbhost-7bd58565d9-p5hzx   1/1   Running  
  0  6h
onap  appc-dgbuilder-68c68ff84b-m65zx0/1   Init:0/1 
  1  6h
onap  clamp-6889598c4-vxdg9  0/1   Init:0/1 
  33 6h
onap  clamp-mariadb-78c46967b8-wg4h5 0/1   
ImagePullBackOff   0  6h
onap  cli-6885486887-9gsnx   0/1   
ImagePullBackOff   0  6h
onap  config 0/1   
Completed  0  6h
onap  consul-agent-56499f9db5-qd87m  1/1   Running  
  3  6h
onap  consul-server-695997745c-27k7p 1/1   Running  
  1  6h
onap  consul-server-695997745c-5rxbp 1/1   Running  
  2  6h
onap  consul-server-695997745c-dmb2b 1/1   Running  
  2  6h
onap  esr-esrgui-568b77d864-z7dvp0/1   
ImagePullBackOff   0  6h
onap  esr-esrserver-85fbfc798b-lwh6l 0/1   
ImagePullBackOff   0  6h
onap  kube2msb-registrator-6cc7f44649-ndwxv  0/1   
ImagePullBackOff   0  6h
onap  log-elasticsearch-6ff5b5459d-6h6fl 1/1   Running  
  0  6h
onap  log-kibana-54c978c5fc-lv9gj1/1   Running  
  0  6h
onap  log-logstash-5f6fbc4dff-bfst2  1/1   Running  
  0  6h
onap  message-router-dmaap-7898949877-t7w74  1/1   Running  
  0  6h
onap  message-router-global-kafka-594b49cf4c-bb2c5   1/1   Running  
  0  6h
onap  message-router-zookeeper-5fbf8b49b4-jjzmg  1/1  

[onap-discuss] OOM errors cannot deploy ONAP

2018-03-03 Thread abdelmuhaimen.seaudi
Hi,

I am trying to deploy onap on an Openstack 64GB RAM VM, using the oom startup 
script from this link 
https://jira.onap.org/secure/attachment/11206/oom_entrypoint.sh

Rancher comes up OK, host is registered.

However, I get some errors while pulling the docker images, and some pods are 
running and rest have errors, and i cannot login to the portal.

I tried also using the version from the wiki at 
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes, but i get similar results.

Where can i find a version of the script that is tested to work OK with 
Openstack  ?


Thanks

Abdelmuhaimen Seaudi
Orange Labs Egypt
Mobile: +2012 84644 733

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss