Devstack Installation Fails with Internal Server Error (HTTP 500)

Eugen Block eblock at
Thu Jun 16 11:04:11 UTC 2022

It can't reach the neutron service, that's what failing here. I'm not  
familiar with devstack, is there any way to verify the basic services  
before deploying trove or is it "all-in-one"? Anyway, in this case I'd  
recommend to check neutron logs and then fix it.

Zitat von KK CHN < at>:

> This is my latest  devstack installation error..   No clues  why it fails
> repeatedly; earlier it was during the uploading stage of the cirros image,
> internal server error ( HTTP 500 ) occurred. This was repeated multiple
> times. So I posted for the first time in this thread.
>  In this iteration for starting afresh, I have removed the stack user and
> /opt/stack directory manually, and freshly created   'stack' user with sudo
> permissions and  /opt/stack  directory with   stack:stack ownership,   and
> fresh git cloned(git clone )  to
> /opt/DEVSTACK_stack   folder and created local.conf  ( attached here) .
> Then executed     ./ .
> Got the following error this time ...   Any clues why it fails here ?
> Platform (on a VM with Debian uname output) :  Linux XenaCtrl1
> 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux
> [image: Trove_installationError.png]
> On Tue, Jun 14, 2022 at 8:46 PM Sean Mooney <smooney at> wrote:
>> On Tue, 2022-06-14 at 06:37 -0700, Dan Smith wrote:
>> > > i hit the same issue the other day if you recall me asking about it.
>> > > didnt check my devstack logs to see if it installed or not but i can
>> > > see if i can repoduce it tomorrow.
>> >
>> > I checked with the OP and they have it installed properly,
>> > system-wide. I was assuming your issue might have been venv (or
>> > ordering) related, but theirs was not. There are some other weird things
>> > going on with their setup, so I'm not so sure.
>> nope, was not useing a vnev or anything special, it just devstack
>> installed normaly more or less
>> but driven by the ansible roles. the run devstack rull litrally just opens
>> a shell and invokes
>> so i dont think there was anything specific ot how i was invoking
>> it.
>> >
>> > --Dan
>> >

More information about the openstack-discuss mailing list