From bbendel at acardo.com Thu Aug 15 07:14:35 2019 From: bbendel at acardo.com (=?UTF-8?Q?Benjamin_Bendel_=7C_acardo_group_AG?=) Date: Thu, 15 Aug 2019 07:14:35 +0000 Subject: [openstack-de] Octavia Amphora-Instance vanishes after getting to ERROR-State References: Message-ID: <0102016c9420d3f0-91807ae5-0935-479f-9536-74a2cd7acc2a-000000@eu-west-1.amazonses.com>     Hi,   is there any solution to access and debug failed instances?     Kind Regards   -------------- next part -------------- An HTML attachment was scrubbed... URL: From dev.faz at gmail.com Fri Aug 16 07:48:52 2019 From: dev.faz at gmail.com (Fabian Zimmermann) Date: Fri, 16 Aug 2019 09:48:52 +0200 Subject: [openstack-de] Octavia Amphora-Instance vanishes after getting to ERROR-State In-Reply-To: <0102016c9420d3f0-91807ae5-0935-479f-9536-74a2cd7acc2a-000000@eu-west-1.amazonses.com> References: <0102016c9420d3f0-91807ae5-0935-479f-9536-74a2cd7acc2a-000000@eu-west-1.amazonses.com> Message-ID: Hi, we could switch to german on openstack-de, but nevertheless ;) Am 15.08.19 um 09:14 schrieb Benjamin Bendel | acardo group AG: > is there any solution to access and debug failed instances? there are some "housekeeping" and "cleanup"-Timeouts. In the past, these timeouts were quite small. I dont know the version of octavia you are using, but maybe you just have to increase these timeouts. As soon as the instances keep running you should be able to connect to the instance with an ssh-key you may set/configure in the octavia.conf Fabian