Re: [onap-discuss] [OOM] vnc portal crashloopbackoff with newest helm/rancher

2018-02-14 Thread FREEMAN, BRIAN D 
The oom rancher/heml intall script installs 2.8 even though I am doing 
Amsterdam so that is probably the problem.

I'll edit the script and only use the amsterdam tested versions of rancher and 
helm.

Is master / beijing stable for some reason I remember reading that not all the 
fixes in the oom amsterdam were in oom beijing yet ?

Brian


From: OBRIEN, FRANK MICHAEL
Sent: Wednesday, February 14, 2018 4:46 PM
To: FREEMAN, BRIAN D <bf1...@att.com>; 'onap-discuss@lists.onap.org' 
<onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] [OOM] vnc portal crashloopbackoff with newest 
helm/rancher

Brian,
  Sorry, first time out of 8h of meetings today.
  Thanks for the diligence  - appreciated

  Beijing will only work down to helm 2.5 because it has tpl templates for 
variable subs (don't exist in helm 2.3) - so you will notice if you downgrade 
helm in master - most pods will fail immediately.

  Vnc-portal comes up for me without changes in both master and amsterdam (last 
tested 4 days ago) in openlab, openstack-private and aws, retesting azure now.  
I have heard about issues with /ect/hosts needing an update  - but this should 
only affect running the apps inside portal inside the image - the container 
should come up.

  We should document anything related to the vnc-portal container being busted 
in
 
https://jira.onap.org/browse/OOM-486<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_OOM-2D486=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=ggVaNloyY_70VEVH7LudZ4_3ygZ4wXOgEm_PxeEREOM=Flp_jEcWhF7FlGBMLn1Rmd4-tRpTexu3T5rZO6Mdgrg=>

  We will be fixing/retrofitting the wiki tomorrow to archive some content and 
make things like config clearer.

  So far tested versions
  Amsterdam (Rancher 1.6.10 (installs Kubernetes 1.7.7), kubectl 1.7.7 (1.8.6 
tested), helm 2.3.0 (client and server), docker 1.12

  Beijing/master (Rancher 1.6.14 (installs Kubernetes 1.8.x, kubectl 1.8.6 
(1.9.2 tested), helm 2.6.0 recommended on client/server - can upgrade to 2.8.0

   Vnc-portal is one of the last to come up because of its dependencies on for 
example vid.

   On the last build for Beijing it comes up with no changes - I don't test 
that links to aai/policy/sdc for example work during the CD test
http://jenkins.onap.info/job/oom-cd/1873/console<https://urldefense.proofpoint.com/v2/url?u=http-3A__jenkins.onap.info_job_oom-2Dcd_1873_console=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=ggVaNloyY_70VEVH7LudZ4_3ygZ4wXOgEm_PxeEREOM=d-Squ0onkYV-sPW7zLsNED-lo5borSdSBzNmIiLJC6w=>
The periodic SDNC failures have a jira and are related to a too small 
readiness check of 5 sec (Mike E. mentioned) - so ignore these for now.

20:08:32 9 pending > 0 at the 44th 15 sec interval
20:08:48 onap-aaf  aaf-c68d8877c-pm47q   
0/1   Running0  13m
20:08:48 onap-portal   vnc-portal-687cdf7845-wxzzt   
0/1   PodInitializing0  13m
20:08:48 onap-sdnc dmaap-listener-78f4cdb695-rtvcg   
0/1   Init:0/1   1  13m
20:08:48 onap-sdnc sdnc-0
0/2   Init:0/1   1  13m
20:08:48 onap-sdnc sdnc-dbhost-0 
0/2   Pending0  13m
20:08:48 onap-sdnc sdnc-dgbuilder-8667587c65-w58mg   
0/1   Init:0/1   1  13m
20:08:48 onap-sdnc sdnc-portal-6587c6dbdf-ng8h7  
0/1   Init:0/1   1  13m
20:08:48 onap-sdnc ueb-listener-65d67d8557-zdd57 
0/1   Init:0/1   1  13m
20:08:48 onap-vfc  vfc-ztevnfmdriver-585d8db4f7-h75ll
0/1   ImagePullBackOff   0  13m
20:08:48 9 pending > 0 at the 45th 15 sec interval
20:09:04 onap-aaf  aaf-c68d8877c-pm47q   
0/1   Running0  13m
20:09:04 onap-sdnc dmaap-listener-78f4cdb695-rtvcg   
0/1   Init:0/1   1  14m
20:09:04 onap-sdnc sdnc-0
0/2   Init:0/1   1  14m
20:09:04 onap-sdnc sdnc-dbhost-0 
0/2   Pending0  14m
20:09:04 onap-sdnc sdnc-dgbuilder-8667587c65-w58mg   
0/1   Init:0/1   1  14m
20:09:04 onap-sdnc sdnc-portal-6587c6dbdf-ng8h7  
0/1   Init:0/1   1  14m
20:09:04 onap-sdnc ueb-listener-65d67d8557-zdd57 
0/1   Init:0/1   1  14m
20:09:04 onap-vfc  vfc-ztevnfmdriver-585d8db4f7-h75ll
0/1   ImagePullBackOff   0  13m



From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.ona

Re: [onap-discuss] [OOM] vnc portal crashloopbackoff with newest helm/rancher

2018-02-14 Thread Michael O'Brien 
Brian,
  Sorry, first time out of 8h of meetings today.
  Thanks for the diligence  - appreciated

  Beijing will only work down to helm 2.5 because it has tpl templates for 
variable subs (don't exist in helm 2.3) - so you will notice if you downgrade 
helm in master - most pods will fail immediately.

  Vnc-portal comes up for me without changes in both master and amsterdam (last 
tested 4 days ago) in openlab, openstack-private and aws, retesting azure now.  
I have heard about issues with /ect/hosts needing an update  - but this should 
only affect running the apps inside portal inside the image - the container 
should come up.

  We should document anything related to the vnc-portal container being busted 
in
 https://jira.onap.org/browse/OOM-486

  We will be fixing/retrofitting the wiki tomorrow to archive some content and 
make things like config clearer.

  So far tested versions
  Amsterdam (Rancher 1.6.10 (installs Kubernetes 1.7.7), kubectl 1.7.7 (1.8.6 
tested), helm 2.3.0 (client and server), docker 1.12

  Beijing/master (Rancher 1.6.14 (installs Kubernetes 1.8.x, kubectl 1.8.6 
(1.9.2 tested), helm 2.6.0 recommended on client/server - can upgrade to 2.8.0

   Vnc-portal is one of the last to come up because of its dependencies on for 
example vid.

   On the last build for Beijing it comes up with no changes - I don't test 
that links to aai/policy/sdc for example work during the CD test
http://jenkins.onap.info/job/oom-cd/1873/console
The periodic SDNC failures have a jira and are related to a too small 
readiness check of 5 sec (Mike E. mentioned) - so ignore these for now.

20:08:32 9 pending > 0 at the 44th 15 sec interval
20:08:48 onap-aaf  aaf-c68d8877c-pm47q   
0/1   Running0  13m
20:08:48 onap-portal   vnc-portal-687cdf7845-wxzzt   
0/1   PodInitializing0  13m
20:08:48 onap-sdnc dmaap-listener-78f4cdb695-rtvcg   
0/1   Init:0/1   1  13m
20:08:48 onap-sdnc sdnc-0
0/2   Init:0/1   1  13m
20:08:48 onap-sdnc sdnc-dbhost-0 
0/2   Pending0  13m
20:08:48 onap-sdnc sdnc-dgbuilder-8667587c65-w58mg   
0/1   Init:0/1   1  13m
20:08:48 onap-sdnc sdnc-portal-6587c6dbdf-ng8h7  
0/1   Init:0/1   1  13m
20:08:48 onap-sdnc ueb-listener-65d67d8557-zdd57 
0/1   Init:0/1   1  13m
20:08:48 onap-vfc  vfc-ztevnfmdriver-585d8db4f7-h75ll
0/1   ImagePullBackOff   0  13m
20:08:48 9 pending > 0 at the 45th 15 sec interval
20:09:04 onap-aaf  aaf-c68d8877c-pm47q   
0/1   Running0  13m
20:09:04 onap-sdnc dmaap-listener-78f4cdb695-rtvcg   
0/1   Init:0/1   1  14m
20:09:04 onap-sdnc sdnc-0
0/2   Init:0/1   1  14m
20:09:04 onap-sdnc sdnc-dbhost-0 
0/2   Pending0  14m
20:09:04 onap-sdnc sdnc-dgbuilder-8667587c65-w58mg   
0/1   Init:0/1   1  14m
20:09:04 onap-sdnc sdnc-portal-6587c6dbdf-ng8h7  
0/1   Init:0/1   1  14m
20:09:04 onap-sdnc ueb-listener-65d67d8557-zdd57 
0/1   Init:0/1   1  14m
20:09:04 onap-vfc  vfc-ztevnfmdriver-585d8db4f7-h75ll
0/1   ImagePullBackOff   0  13m



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of FREEMAN, BRIAN D
Sent: Tuesday, February 13, 2018 14:24
To: 'onap-discuss@lists.onap.org' <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [OOM] vnc portal crashloopbackoff with newest 
helm/rancher

I started the vnc-portal docker image separately and it comes up cleanly.
Had to manually update /etc/hosts

Must be something in the helm dependencies causing the crashloopbackoff.

Brian


From: FREEMAN, BRIAN D
Sent: Tuesday, February 13, 2018 10:32 AM
To: 'onap-discuss@lists.onap.org' 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: RE: [OOM] vnc portal crashloopbackoff with newest helm/rancher



root@onapoom3:/home/onapuser/ONAP# docker ps --all | grep vnc
db9a2c7ec5b7
dorowu/ubuntu-desktop-lxde-vnc@sha256:7817dda9f734703eefd73a895d69411f2983e186c861048667fcd92e15
 af612d  "/startup.sh"  
   2 minutes ago   Exited (143) 2 minutes ago   

k8s_vnc-portal_vnc-portal-56c8b774fb-dkm4r_o

Re: [onap-discuss] [OOM] vnc portal crashloopbackoff with newest helm/rancher

2018-02-13 Thread FREEMAN, BRIAN D 
I started the vnc-portal docker image separately and it comes up cleanly.
Had to manually update /etc/hosts

Must be something in the helm dependencies causing the crashloopbackoff.

Brian


From: FREEMAN, BRIAN D
Sent: Tuesday, February 13, 2018 10:32 AM
To: 'onap-discuss@lists.onap.org' 
Subject: RE: [OOM] vnc portal crashloopbackoff with newest helm/rancher



root@onapoom3:/home/onapuser/ONAP# docker ps --all | grep vnc
db9a2c7ec5b7
dorowu/ubuntu-desktop-lxde-vnc@sha256:7817dda9f734703eefd73a895d69411f2983e186c861048667fcd92e15
 af612d  "/startup.sh"  
   2 minutes ago   Exited (143) 2 minutes ago   

k8s_vnc-portal_vnc-portal-56c8b774fb-dkm4r_onap-portal_9d56a918-1075-11e8-b191-026a60b
 a687a_132
439f6921a8a2gcr.io/google_containers/pause-amd64:3.0

 "/pause"  11 hours agoUp 11 hours  

k8s_POD_vnc-portal-56c8b774fb-dkm4r_onap-portal_9d56a918-1075-11e8-b191-026a60ba687a_0


From: FREEMAN, BRIAN D
Sent: Tuesday, February 13, 2018 9:00 AM
To: onap-discuss@lists.onap.org
Subject: [OOM] vnc portal crashloopbackoff with newest helm/rancher

Michael,

I'm using the oom _rancher_setup_1.sh 
(https://wiki.onap.org/download/attachments/8227431/oom_rancher_setup_1.sh?version=6=1516919271000=v2)

And vnc portal isnt coming up. Cant really grab any logs on it.

Most of the other components are up (had to change the public IP for dmaap in 
SDC AUTO.json to be the dmaap.onap-message-router comma and comma quoated 
strings.

Do I need to revert to the earlier version of helm ?

Brian

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

Re: [onap-discuss] [OOM] vnc portal crashloopbackoff with newest helm/rancher

2018-02-13 Thread FREEMAN, BRIAN D 


root@onapoom3:/home/onapuser/ONAP# docker ps --all | grep vnc
db9a2c7ec5b7
dorowu/ubuntu-desktop-lxde-vnc@sha256:7817dda9f734703eefd73a895d69411f2983e186c861048667fcd92e15
 af612d  "/startup.sh"  
   2 minutes ago   Exited (143) 2 minutes ago   

k8s_vnc-portal_vnc-portal-56c8b774fb-dkm4r_onap-portal_9d56a918-1075-11e8-b191-026a60b
 a687a_132
439f6921a8a2gcr.io/google_containers/pause-amd64:3.0

 "/pause"  11 hours agoUp 11 hours  

k8s_POD_vnc-portal-56c8b774fb-dkm4r_onap-portal_9d56a918-1075-11e8-b191-026a60ba687a_0


From: FREEMAN, BRIAN D
Sent: Tuesday, February 13, 2018 9:00 AM
To: onap-discuss@lists.onap.org
Subject: [OOM] vnc portal crashloopbackoff with newest helm/rancher

Michael,

I'm using the oom _rancher_setup_1.sh 
(https://wiki.onap.org/download/attachments/8227431/oom_rancher_setup_1.sh?version=6=1516919271000=v2)

And vnc portal isnt coming up. Cant really grab any logs on it.

Most of the other components are up (had to change the public IP for dmaap in 
SDC AUTO.json to be the dmaap.onap-message-router comma and comma quoated 
strings.

Do I need to revert to the earlier version of helm ?

Brian

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

[onap-discuss] [OOM] vnc portal crashloopbackoff with newest helm/rancher

2018-02-13 Thread FREEMAN, BRIAN D 
Michael,

I'm using the oom _rancher_setup_1.sh 
(https://wiki.onap.org/download/attachments/8227431/oom_rancher_setup_1.sh?version=6=1516919271000=v2)

And vnc portal isnt coming up. Cant really grab any logs on it.

Most of the other components are up (had to change the public IP for dmaap in 
SDC AUTO.json to be the dmaap.onap-message-router comma and comma quoated 
strings.

Do I need to revert to the earlier version of helm ?

Brian

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