Hello all
I’ve just tried out Microstack for the first time, trying to build an AIO single host for a demo of Ansible integration. I love the idea of Microstack - the setup and initialization is so quick and easy.
Unfortunately this is as far as my first foray into Microstack has gone - I can’t get it to run any VM instances once it’s installed. I have had a look through the logs, and I see errors relating to allocation of the block device, and also port binding in Neutron. This is a simple, single node setup based on Ubuntu Server 20.04. I’ve followed the 3 step install process at https://microstack.run/ for single Linux hosts, but no joy.
Are there additional system requirements that are not documented here, or additional setup steps that are required in certain environments? I don’t believe mine is anything special, but I feel like this should have been so simple yet wasn’t.
Happy to submit logs or anything that would help debug this.
Many thanks
James
Hi James,
Thanks for reaching out. Sorry that MicroStack is not working for you. It’d be a little bit helpful to understand how you installed MicroStack (specifically which command, as many users miss the --devmode flag required) and a bit more detail on what errors you are seeing in the logs.
Also, please be aware that persistent volume support is still considered experimental so you may run into some issues here; but we are interested in the issues that you might encounter.
Hi Billy
Thanks for your reply and for reaching out. This morning the node won’t come up at all so I haven’t been able to retrieve any relevant errors for you - the nova.log is full of errors, but Horizon won’t load this morning so I think I’ll wipe the install and start again.
For reference, I installed on a minimal Ubuntu Server 20.04 system. In case it’s relevant, the system was built without LVM, and using an ext4 root filesystem (no secondary drive or partition).
I installed using the following commands (all run as root):
apt update && apt -y upgrade && apt autoremove
snap install microstack --devmode --beta
microstack init --auto --control
snap get microstack config.credentials.keystone-password
The errors I saw (working from memory) seemed to be related to storage/volumes, and I found the following command on the forums (also was conscious LVM was not enabled on my system) here so ran this:
microstack init --auto --control --setup-loop-based-cinder-lvm-backend --loop-device-file-size 50
However this didn’t make anything better.
Given the broken status of my node this morning, I intend to wipe it and rebuild it. Before I do so, can you see anything wrong with the commands/initial system I’ve provided here? I’ll make sure this is right before I run the next install, and then will make sure I capture log files and pertinent details if problems persist. For example are there requirements on LVM or root filesystem structure? Do I need a secondary drive for Microstack to store data on?
Many thanks
James
Hi James,
Apologies for the delayed response here. In my setup I’m not using LVM for the host system, but I would avoid setting up the loop based cinder lvm backend. This essentially creates a loopback device and creates the necessary VGs from that. To keep it simple, I’d start out without the lvm backend enabled and go from there (which is what it seems you were trying to do).
Since its been some time, have you reinstalled it? How are things working out?
Hi Billy
Thanks for checking in and for your advice. I was holding off on the rebuild until I heard from you as I’m not intimately familiar with Microstack.
So today I rebuilt from a fresh Ubuntu Server 20.04 image - results were slightly different in that I can now upload an image - last time this was broken so there has been an incremental improvement since the last attempt.
However two things I noticed. First was, I tried to create a new project, which resulted in the following error:
Error: Could not find default role "_member_" in Keystone
I continued under the “out of the box” admin project, and tried to create a new instance. This started off well, but then failed with the error:
Error: Failed to perform requested operation on instance "test", the instance has an error status: Please try again later [Error: Build of instance f63b9d57-dbaa-4840-b225-222bf9081ec9 aborted: Volume 5e5ec647-438c-4745-b65a-7c6f69f660bb did not finish being created even after we waited 0 seconds or 1 attempts. And its status is error.].
A quick dig through the log files revealed a large number of stack traces in nova.log, but these messages stood out:
nova.exception.PortBindingFailed: Binding failed for port 94bb1615-14a9-44a9-8551-d45c1ef9f524, please check neutron logs for more information.
oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 00c82d14e3324534b7f6a1de7fed7bf9
I’m not sure what these mean or how to resolve them - and advice appreciated!
Kind regards
James
I’ll give this a spin myself from a fresh machine to see if I can see similar results. I’m curious what the specs you have for the machine you are installing MicroStack on?
The default role “_member_” issue is bug 1861371 and can be worked around by simply creating the role in Horizon or using the CLI.
Looking at nova log files is the right first step to see what’s going on. I’d be interested in what the other stack traces are, but the PortBindingFailed message essentially indicates that its not able to plug a network into the instance being launched. You’d have to look at the neutron-api logs to get some more information regarding why the PortBindingFailed.
