[Starlingx-discuss] issue debug on 1917308
Chen, Haochuan Z
haochuan.z.chen at intel.com
Fri Mar 19 15:28:27 UTC 2021
Hi bob
I comment on this bug, add my debug find.
https://bugs.launchpad.net/starlingx/+bug/1917308
After host-swact, and quickly type in command "system application-apply stx-openstack", container tiller in pod armada-api will list installed release saved in postgres. But this list request will be failed with this log. 5432 is postgres listen port. 172.16.192.176 is armada-api pod cluster ip.
2021-03-01T11:38:56.600564874Z stderr F [storage/driver] 2021/03/01 11:38:56 list: failed to list: write tcp 172.16.192.176:35854->10.10.59.10:5432: write: broken pipe
And after a while it will recovery, then "system application-apply", it will succeed.
Any idea about this, maybe after host-swact, postgres is still launching and not ready for connection?
You can reproduce this issue with latest daily build.
BR!
Martin, Chen
IOTG, Software Engineer
021-61164330
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20210319/4053d707/attachment.html>
More information about the Starlingx-discuss
mailing list