MicroStack

The instructions to deploy microstack on a multipass vm fail

Bug #2024992 reported by John Lloyd Olsen
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MicroStack
New
Undecided
Unassigned
OpenStack Snap
New
Undecided
Unassigned

Bug Description

On a fresh Ubuntu 22.04 host, I follow the instructions on https://microstack.run/. I create the required multipass vm and as I have previously found some packages were missing (and I blame Canonical for this) I issue: sudo apt update && sudo apt install -y openvswitch-switch-dpdk python3-neutronclient python3-oauth2client python3-openstackclient python3-pymysql python3-novaclient && sudo lxd init and complete the initialisation of lxd as required. I continue to follow the instructions to end with:

ubuntu@microstack:~$ sunbeam cluster bootstrap --accept-defaults
Sunbeam Cluster not initialized
An unexpected error has occurred. Please run 'sunbeam inspect' to generate an inspection report.
Error: no close frame received or sent

Assuming this may mean simply a badly completed process which may actually have completed well enough to be workable, I do the following:

ubuntu@microstack:~$ sunbeam configure --accept-defaults --openrc demo-openrc
An unexpected error has occurred. Please run 'sunbeam inspect' to generate an inspection report.
Error: Leader for application 'keystone' is missing from model 'openstack'

If I omit to install the aforementioned packages I get a worse result.

So I run 'sunbeam inspect' only to find

ubuntu@microstack:~$ sunbeam inspect
⠋ Getting charm logs for openstack model ... ERROR model sunbeam-controller:microstack/0a3aaf7e-5724-4a2b-806a-bfcc5a397c51 not found
Error: Command '['/snap/openstack/182/juju/bin/juju', 'debug-log', '--model', '0a3aaf7e-5724-4a2b-806a-bfcc5a397c51', '--replay', '--no-tail']' returned non-zero exit status 2.

Why does Canonical publish instructions that persistently fail?

Revision history for this message
John Lloyd Olsen (johnnoe1958) wrote :

I'd like you people to know I also spent most of my weekend trying to install charmed kubernetes with nothing but repeated failure. You obviously do not bother to test your instructions against fresh machines that are likely to be similar to what developers will be using after a fresh install of the OS.

Why do you not test your own instructions properly?

Basically, the longer I live (I am 65) the more disgusted I am becoming with Canonical's Community offerings. You are not doing this section of your business adequately. Is this because accountants are running your software business for you?

John Olsen

Revision history for this message
John Lloyd Olsen (johnnoe1958) wrote :

Or is it because you 4 people: Olsen, Bryant, Mourereau and Matulis are simply doing a half-hearted incompetent job?

John Olsen

Revision history for this message
Billy Olsen (billy-olsen) wrote :

Hi John,

I'm sorry that you are having troubles installing the sunbeam Microstack. I'm not quite sure which challenges you have run into, but I'd like to try and recreate these and fix them so that you don't run into challenges like this. First of all, thank you for raising a bug letting us know of your challenges.

You indicate that you have found that some previous packages were missing and you have chosen to install the following packages:

openvswitch-switch-dpdk python3-neutronclient python3-oauth2client python3-openstackclient python3-pymysql python3-novaclient

How did you come about choosing those packages? When you said you you have found these packages missing, how did you determine these packages were missing? The instructions do not mention these packages because they are not necessary.

The error message shown:
> Error: no close frame received or sent.

Indicates to me that there is some sort of networking issue in this particular configuration. It's not quite clear what the challenge is. Could you please re-run the sunbeam cluster bootstrap command as follows, so we can get some more verbose debugging output? The -v will add verbose output on the commandline to give us a bit of a sense of what's going on.

sunbeam -v cluster bootstrap --accept-defaults

Your other error that occurred when running the configure command - I'll raise a separate bug for that and spin it out from this one. The sunbeam configure command should certainly determine that the bootstrap command has been run or not and provide a more meaningful message.

Revision history for this message
John Lloyd Olsen (johnnoe1958) wrote :

My computer is a 24 core, 128GB computer with INTEL 12TH GEN CORE I9-12900K 3.20GHZ DESKTOP PROCESSOR with a main 2TB HDD and a secondary 1TB HDD.

Revision history for this message
Billy Olsen (billy-olsen) wrote :

I have raised bug #2024996 for the configure step not checking that its been bootstrapped.

I have also started an installation following the exact instructions from the microstack.run site and it appears to be working as the control plan installation is progressing along.

I have started a second installation with the additional packages and lxd initialization step to see if I can recreate the scenario with the error that you have run into.

Revision history for this message
Billy Olsen (billy-olsen) wrote :

Note, bug #1961192 looks to be related to the error that is reported around the "Error: no close frame received or sent." I am suspicious that the pylibjuju connection is not closing out the connection correctly as referenced in the bug - which then leads to this error that is seen.

Revision history for this message