[Starlingx-discuss] [Containers] Deployment status

[Perez Carranza, Jose]

Mingyuan

Yes I have only set the Docker proxies as said on the documentation "Environment="HTTP_PROXY=<your_proxy>" "HTTPS_PROXY=<your_proxy>" "NO_PROXY=localhost,127.0.0.1,192.168.204.2", I did not set system proxies. 

Regards,
José


> -----Original Message-----
> From: Qi, Mingyuan
> Sent: Wednesday, January 30, 2019 7:25 PM
> To: Perez Carranza, Jose <jose.perez.carranza at intel.com>; starlingx-
> discuss at lists.starlingx.io
> Subject: RE: [Starlingx-discuss] [Containers] Deployment status
> 
> Jose,
> 
> Did you set proxy in system env variable?
> I faced that issue once that 192.168.204.2 is not added to no_proxy of system
> env variable.
> Actually system proxy(not the same as docker proxy) is not needed if you are
> not going to access internet from host.
> 
> Mingyuan
> 
> 
> -----Original Message-----
> From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com]
> Sent: Thursday, January 31, 2019 6:31
> To: starlingx-discuss at lists.starlingx.io
> Subject: [Starlingx-discuss] [Containers] Deployment status
> 
> Hi All
> 
> ** Virtual Environment **
> 
> I'm working on setting up a StarlingX deployment with containers as
> described on [1] using proxies but I have faces some issues described below:
> 
> - I have successfully completed all the steps until  "system application-apply
> stx-openstack" when the system becomes unstable, the application-apply
> gets freezed in random pods until timeout of 30 min is reached, I discovered
> that killing armada process and start again the "system application-apply"
> the application  advance until again is freezed in a random pod.  After some
> cycles the application is successfully completed.
> 
> Here is a log [2] of one point when the process is freeze, the error is always
> the same, the only element that  changes is the pod and its random, not
> always is the same pod.
> 
> =====
> 019-01-30 17:24:13.364 11824 ERROR sysinv.conductor.kube_app [-]
> Received a false positive response from Docker/Armada. Failed to apply
> application manifest /manifests/stx-openstack-manifest-no-tests.yaml: 2019-
> 01-30 16:54:07.367 20554 DEBUG armada.handlers.document [-] Resolving
> reference /manifests/stx-openstack-manifest-no-tests.yaml.
> resolve_reference /usr/local/lib/python3.5/site-
> packages/armada/handlers/document.py:49
> =====
> 
> -After is completed correctly I'm receiving failures on "Verify the cluster
> endpoints" when running `openstack endpoint list`, I updated the .yml file
> with the correct password but connection is not established correctly. Here is
> the output [3].
> 
> ======
> controller-0:~$ openstack  endpoint list Failed to discover available identity
> versions when contacting http://keystone.openstack.svc.cluster.local/v3.
> Attempting to parse version from URL.
> Unable to establish connection to
> http://keystone.openstack.svc.cluster.local/v3/auth/tokens:
> HTTPConnectionPool(host='keystone.openstack.svc.cluster.local', port=80):
> Max retries exceeded with url: /v3/auth/tokens (Caused by
> NewConnectionError('<requests.packages.urllib3.connection.HTTPConnectio
> n object at 0x7fe65ffb90d0>: Failed to establish a new connection: [Errno -3]
> Temporary failure in name resolution',)) ======
> 
> 1. https://wiki.openstack.org/wiki/StarlingX/Containers/Installation
> 2. http://paste.openstack.org/show/744277
> 3. http://paste.openstack.org/show/744281
> 
> Regards,
> José
> 
> 
> 
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss