[Starlingx-discuss] [Containers] Deployment status

Perez Carranza, Jose jose.perez.carranza at intel.com
Fri Feb 1 21:27:17 UTC 2019


Mingyuan

After applying workaround you mentioned I only see the freeze one time, on glance pod 30%, after timeout expired I ran again the apply and everything worked correctly without any freeze until completed successfully.  

Regards,
José


> -----Original Message-----
> From: Qi, Mingyuan
> Sent: Friday, February 1, 2019 1:11 AM
> To: Perez Carranza, Jose <jose.perez.carranza at intel.com>; starlingx-
> discuss at lists.starlingx.io; Al.Bailey at windriver.com; Wensley, Barton
> <Barton.Wensley at windriver.com>
> Subject: RE: [Starlingx-discuss] [Containers] Deployment status
> 
> Jose,
> 
> Looking into your log, it seems that coredns is not ready.
> Here is the workaround for it:
> 1. kubectl -n kube-system edit configmap coredns 2. remove "loop" line and
> save 3. kubectl -n kube-system delete rs {your-coredns-replicaset-name}
> 
> Bart & Al,
> 
> It's seems to be a real issue for users behind a proxy which I guess coredns is
> not able to access external nameserver and falls in loop.
> Could user specified nameserver to be updated to coredns?
> 
> Mingyuan
> 
> 
> -----Original Message-----
> From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com]
> Sent: Friday, February 1, 2019 1:31
> To: starlingx-discuss at lists.starlingx.io
> Subject: Re: [Starlingx-discuss] [Containers] Deployment status
> 
> Hi,
> 
> I did some tests with the most recent ISO (01/31) that has already the
> changes to add a proxy on  config_controller, still facing the below
> mentioned issues, I created a Launchpad [1] to track this.
> 
> https://bugs.launchpad.net/starlingx/+bug/1814142
> 
> Regards,
> José
> 
> > -----Original Message-----
> > From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com]
> > Sent: Wednesday, January 30, 2019 4:31 PM
> > 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.HTTPConnecti
> > o 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
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss


More information about the Starlingx-discuss mailing list