Installation of single user microstack in vm fails

Bug #2048379 reported by Bee
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Snap
Triaged
High
Unassigned

Bug Description

I am following the instructions on:
https://microstack.run/#get-started
to install on Ubuntu 22.04.3 LTS

1. Install Multipass
    sudo snap install multipass

2. Get a fresh VM with Ubuntu 22.04 LTS
    multipass launch --name microstack --cpus 4 --memory 16G --disk 50G && multipass shell microstack

3. Install MicroStack
    sudo snap install openstack

4. Prepare a machine
    sunbeam prepare-node-script | bash -x && newgrp snap_daemon

5. Bootstrap OpenStack
    sunbeam cluster bootstrap --accept-defaults

resulting in:

Error: Host FQDN and Hypervisor hostname perceived by libvirt are different, check hostname -fand/etc/hosts file

Others are also reporting this error online.
- Benjamin

Revision history for this message
Peter Mattingly (peter-mattingly) wrote (last edit ):

I also have this issue, which occurs in exactly the same way when following the "Try MicroStack" instructions at https://microstack.run/#get-started.

Edit:

This issue occurs on both an existing WSL installation, and on a freshly installed Jammy instance.

Revision history for this message
mohsen seyedkazemi ardebili (mohsenseyedkazemi) wrote :

I have the same issue.

Changed in snap-openstack:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Billy Olsen (billy-olsen) wrote :

I confirm that I too have seen this issue. The problem stems from a check where the sunbeam code is trying to compare the hostnames for libvirt and the system itself. The utils.get_hypervisor_hostname() returns 'microstack' and the utils.get_fqdn() method returns 'microstack.multipass'.

There are fundamentally two different bits of logic that are being used which is causing the problem here; sunbeam.utils.get_fqdn() and sunbeam.utils.get_hypervisor_hostname(). There are comments within the method that clearly indicate that they are different.

As a work around, you can set the hostname to the fqdn:

sudo hostnamectl set-hostname microstack.multipass
sudo systemctl restart systemd-resolved

And then try again.

Revision history for this message
Khairul Aizat Kamarudzzaman (fenris) wrote :

work around #3 works for me

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.