Hi, 

Make sure you are using the helm chart published the same date of that ISO.

Also the output of “helm list” can help, as well as “kubectl get pods -n openstack”

If there is a pod in a failure state I usually just kill it (there’s for sure a more elegant way),

“kubectl delete pod <pod name> -n openstack”

Also, kubectl describe pod and kubectl logs can help.

-Erich 
--
Sent from Yandex.Mail for mobile

18.04.2019, 09:52, "Miller, Frank" <frank.miller@windriver.com>:

Saul:

I'll let the community members more familiar with how to debug to answer specific debug questions, but it looks like you are hitting this LP reported in sanity:
https://bugs.launchpad.net/starlingx/+bug/1825045

That one does not yet have a solution.

Frank

-----Original Message-----
From: Saul Wold [mailto:sgw@linux.intel.com]
Sent: Wednesday, April 17, 2019 10:49 PM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Trying to debug a stx-openstack-apply failure


Hi Folks,

I have been trying to get a deployment up in a libvirt/qemu environment (non-proxy). I am seeing the following issue. I am using the image that passed (mostly) Sanity Test on Monday 4/15 [0].

I am setting this up in AIO-Simplex mode, I have not setup any kind of registry. It seems to start up all the contains and kubectl get pods shows all the pods Running or Completed. I retrieved the stx-openstack-apply.log from armada as recommended by the Container Debug FAQ [1].
I see multiple Errors that the Application apply aborted due to what seems like download failures. As I said, I am not behind any proxy or firewall.

It seems to fail during processing chart: osh-openstack-neutron at 65%

Not sure what the next steps are to debug this issue.

Thanks
    Sau!


[0]
http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190415T233001Z/
[1] https://wiki.openstack.org/wiki/StarlingX/Containers/FAQ
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss