On 12/07/2017 12:39 PM, Wouter Verhelst wrote:
> - After doing all that, I can go through the "Launch instance" wizard in
> the webinterface. It accepts my choices; but when it gets around to
> actually trying to spawn the VM, the machine becomes unresponsive.
> Once it starts being responsive again, it says "No valid host was
> found. There are not enough hosts available." It's not clear to my
> what exactly went wrong; this may be fixed by some configuration, or
> it may not.
The "No valid host was found" should be interpreted as "no compute host
is working, I can't start the VM". Since you have only one compute node,
it means that host doesn't work.
Have you made sure to replace nova-compute-kvm by nova-compute-qemu,
since you're in a VM? After doing so, make sure to restart nova-compute.
> At this point, I can't remove the instance anymore either,
> with a "CSRF token missing or incorrect" error message.
This is a known bug in Horizon in Stretch, due to an incompatibility
with Django 1.10. It has been fixed since, but I haven't investigated in
which commit, so I could backport it.
Instead of selecting the instance with the checkbox, just click on the
dropdown and click on terminate. This should work.
> It feels like the system is fairly close to a working setup, though.
Once you've fixed the nova issue, I'm quite sure you'll have trouble
with the networking (unless you've followed the install guide to make
your networking setup). In any case, just look in your
/var/log/{nova,neutron}/*.log when starting the VM. And try without
horizon, with something like this:
openstack server create --image \
$(openstack image list --format=csv | q -d , \
-H 'SELECT ID FROM -') --flavor $(openstack flavor \
list --format=csv | q -d , -H \
'SELECT ID FROM - WHERE `Name`="m1.tiny"') \
--nic net-id=$(openstack network list --format=csv \
| q -d , -H \
'SELECT ID FROM - WHERE `Name`="demo-net"') \
test-server.debian.net
(you can adapt of course, with network name, image name, and flavor)
Cheers,
Thomas Goirand (zigo)
