Hi Mandeep,

Thanks for your response 😊 I see in the full command below that is it also 
trying to run the host command on portalapps, sdc, policy, cli, aai, and vid. 
In my setup, I do not have policy and cli installed (I just have deployed aai, 
appc, mr, mso, robot, sdc, sdnc, and vid). Do you think that it may be the 
reason why the /ubuntu-init/hosts file/dir is not getting created?

Thanks,
Hector

From: Mandeep Khinda <mandeep.khi...@amdocs.com>
Sent: Wednesday, May 09, 2018 5:53 PM
To: ANAPAN-LAVALLE, HECTOR A <ha0...@att.com>; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [onap-discuss[[oom[[portal]

I missed the Amsterdam part.  Sorry my bad ☚

That /ubuntu-init/hosts file is generated by the Init container that runs 
before the main VNC container can start.
The ubuntu-init:1.0.0 should be run in Amsterdam and this container uses the 
“host” command to extract DNS IPs from the other running containers to populate 
IP to DNS aliases:
         {
              "command": ["/bin/sh","-c"],
              "args": ["echo `host sdc-be.{{ .Values.nsPrefix }}-sdc | awk 
''{print$4}''` sdc.api.be.simpledemo.onap.org  >> /ubuntu-init/hosts; echo 
`host portalapps.{{ .Values.nsPrefix }}-portal | awk ''{print$4}''` 
portal.api.simpledemo.onap.org  >> /ubuntu-init/hosts; echo `host pap.{{ 
.Values.nsPrefix }}-policy | awk ''{print$4}''` policy.api.simpledemo.onap.org  
>> /ubuntu-init/hosts; echo `host sdc-fe.{{ .Values.nsPrefix }}-sdc | awk 
''{print$4}''` sdc.api.simpledemo.onap.org  >> /ubuntu-init/hosts; echo `host 
vid-server.{{ .Values.nsPrefix }}-vid | awk ''{print$4}''` 
vid.api.simpledemo.onap.org >> /ubuntu-init/hosts; echo `host sparky-be.{{ 
.Values.nsPrefix }}-aai | awk ''{print$4}''` aai.api.simpledemo.onap.org  >> 
/ubuntu-init/hosts; echo `host cli.{{ .Values.nsPrefix }}-cli | awk 
''{print$4}''` cli.api.simpledemo.onap.org  >> /ubuntu-init/hosts"],
              "image": "{{ .Values.image.ubuntuInit }}",
              "imagePullPolicy": "{{ .Values.pullPolicy }}",
              "name": "vnc-init-hosts",
              "volumeMounts": [
                {
                  "name": "ubuntu-init",
                  "mountPath": "/ubuntu-init/"
                }
              ]
          }
After that is done, the main container has a post start lifecycle hook that 
appends the contents of /ubuntu-init/hosts to /etc/hosts.

That is what is supposed to happen and I don’t think anything has changed on 
the Amsterdam branch so I am not sure what is going on.
Mandeep


From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of Mandeep Khinda 
<mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>
Date: Wednesday, May 9, 2018 at 5:42 PM
To: "ANAPAN-LAVALLE, HECTOR A" <ha0...@att.com<mailto:ha0...@att.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [onap-discuss[[oom[[portal]

Hi Hector,
For the Beijing release on OOM  the VNC pod was obsoleted in favour of direct 
client side access.

I captured some notes on it in the link below after a couple of questions on 
usage have come my way.
https://wiki.onap.org/display/DW/2018/05/09/Accessing+ONAP+Portal+using+OOM+and+a+Kubernetes+Cluster<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_2018_05_09_Accessing-2BONAP-2BPortal-2Busing-2BOOM-2Band-2Ba-2BKubernetes-2BCluster&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FXSTHna6MzE3ojMq3gr1yQ&m=6I_uohvtcv-gAwkOIMLA9koGTGPHCa4wQN62dPDLOxE&s=hFXVMQXWFQQ1Hjkq4N48tjFmo0A2ayKGktgehnrjwsQ&e=>

Let me know if that doesn’t work or if you have any other questions.
Mandeep

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "ANAPAN-LAVALLE, HECTOR A" <ha0...@att.com<mailto:ha0...@att.com>>
Date: Wednesday, May 9, 2018 at 3:22 PM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] [onap-discuss[[oom[[portal]

Hi,

Trying to deploy an ONAP Portal (Amsterdam release) deployment on a 
Rancher/7-node K8S cluster, and the vnc-console does not start and stays in the 
“CrashLoopBackOff” State.

Exec lifecycle hook ([/bin/sh -c mkdir -p /root/.mozilla/firefox/onap.default; 
cp /root/.init_profile/profiles.ini /root/.mozilla/firefox/; echo 
'user_pref("browser.tabs.remote.autostart.2", false);' > 
/root/.mozilla/firefox/onap.default/prefs.js; cat /ubuntu-init/hosts >> 
/etc/hosts]) for Container "vnc-portal" in Pod 
"vnc-portal-7bd4ddd978-k6v4x_onap-portal(877dede2-53b3-11e8-8933-02cc6f206a12)" 
failed - error: command '/bin/sh -c mkdir -p 
/root/.mozilla/firefox/onap.default; cp /root/.init_profile/profiles.ini 
/root/.mozilla/firefox/; echo 'user_pref("browser.tabs.remote.autostart.2", 
false);' > /root/.mozilla/firefox/onap.default/prefs.js; cat /ubuntu-init/hosts 
>> /etc/hosts' exited with 1: cat: /ubuntu-init/hosts: No such file or 
directory , message: "cat: /ubuntu-init/hosts: No such file or directory\n"

Has anybody come across/know how why this error is happening?

Thanks,
Hector
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FXSTHna6MzE3ojMq3gr1yQ&m=6I_uohvtcv-gAwkOIMLA9koGTGPHCa4wQN62dPDLOxE&s=sBAMPiDntGI6EA6f45aVPT9oiRBhfRTTEcjPFen0wnc&e=>
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FXSTHna6MzE3ojMq3gr1yQ&m=6I_uohvtcv-gAwkOIMLA9koGTGPHCa4wQN62dPDLOxE&s=sBAMPiDntGI6EA6f45aVPT9oiRBhfRTTEcjPFen0wnc&e=>
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to