I successfully installed openstack nova-lxd on a kvm virtual machine using conjure-up.
After a VM shutdown; when I start the VM openstack doesn't start. lxc list shows one instance in "RUNNING" state and all the other in "STOPPED" state.
How can I start the other instances?
I have this exact same problem. I installed a brand new copy of Ubuntu 16.04 on my server, updated all the packages, then the only thing I installed was conjure-up and used that to install lxc openstack.
lxc list
showed all of the instances as up and running, I could login to the openstack dashboard, it was great. Then I rebooted...nowlxc list
shows all but one instance as not running. @gangstaluv to answer your questions in my environment:When I try that I get an error which probably explains why things didn't just come back up on their own:
I'm not sure how to proceed. Is there something else I could check? I've re-installed Ubuntu and conjure-up in case I had done something wrong but every time it works perfectly until a reboot, then it ends up in this state again.
EDIT-1: I didn't think to add the
lxc info
that it said to look at, adding that now.EDIT-2: I just fixed mine!
After much research I discovered the command
lxc profile show
From the output of the
lxc info --show-log juju-ec5bf1-0
I surmised that somehow juju (or some other component) saw my other nic (I'm running this on real hardware as opposed to Mirto Busico on a VM if I read correctly) and was looking for a bridge called conjureup0 that didn't exist. I suspect there is a bug somewhere which is why this was not created. I think I could have done one of two things to fix this. 1) create the missing bridge 2) remove the eth1 device from the profile. I chose the latter.$ lxc profile device remove juju-conjure-up-openstack-novalxd-561 eth1
Rebooted, and now
lxc list
shows all my instances are up and running as expected and my dashboard works again.@gangstaluv: retrying to do the install from scratch in March ends up with conjureup0 surviving the reboot.
After the reboot all the lxd containers are up and running but the rabbitmq-server in in error (for this I'll open another thread)
I also faced this kind of issue before, mostly likely the problem is with the network setting. By default, the value of MTU size should 1500 while first time deploy conjure-up openstack. My solution is to change the MTU size inside lxc profile configuration. You may also try on that.