ubuntulxdmaas

Trouble adding LXD Clusters to MAAS


Trouble with Setting Up LXD Clusters in MAAS

Hello! I have been working with maas to try and setup a LXD cluster.

Setup

Versions

$ snap list | grep maas
maas                       3.2.0~beta6-11974-g.58f181df4  21449  3.2/beta         canonical**  -
maas-cli                   0.6.5                          13     latest/stable    canonical**  -
maas-test-db               12.4-22-g.aed1dfe              91     3.1/stable       canonical**  -

(This was also tested with 3.1/stable with the same results.)

$ cat /etc/os-release 
PRETTY_NAME="Ubuntu 22.04 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

$ snap list | grep lxd
lxd     5.2-79c3c3b  23155  latest/stable  canonical**  -

What I have tried

I have tried following the following articles:

I am able to get the LXD cluster going using lxd init on the first Dell PowerEdge server and following the prompts. I then add the other two PowerEdge's using lxd init again and copy/pasting their join tokens. However, when I add the LXD host from the maas KVM page, it just shows up as a single cluster.

Related Info

MAAS Dashboard:

$ maas admin machines read | jq 'insert jq magic here'
HOSTNAME      SYSID   POWER    STATUS    OWNER  TAGS             POOL     VLAN      FABRIC    SUBNET
--------      -----   -----    ------    -----  ----             ----     ----      ------    ------
fun-shad      ncw7a4  on       Deployed  ben    metal            default  untagged  fabric-1  
moral-dassie  krrkfk  on       Deployed  ben    metal            default  untagged  fabric-1  
new-drum      p68mcg  on       Deployed  ben    metal            default  untagged  fabric-1  

LXD Cluster:

root@fun-shad:~# lxc cluster list
+--------------+--------------------------+-----------------+--------------+----------------+-------------+--------+-------------------+
|     NAME     |           URL            |      ROLES      | ARCHITECTURE | FAILURE DOMAIN | DESCRIPTION | STATE  |      MESSAGE      |
+--------------+--------------------------+-----------------+--------------+----------------+-------------+--------+-------------------+
| fun-shad     | https://10.113.1.73:8443 | database-leader | x86_64       | default        |             | ONLINE | Fully operational |
|              |                          | database        |              |                |             |        |                   |
+--------------+--------------------------+-----------------+--------------+----------------+-------------+--------+-------------------+
| moral-dassie | https://10.113.1.74:8443 | database        | x86_64       | default        |             | ONLINE | Fully operational |
+--------------+--------------------------+-----------------+--------------+----------------+-------------+--------+-------------------+
| new-drum     | https://10.113.1.72:8443 | database        | x86_64       | default        |             | ONLINE | Fully operational |
+--------------+--------------------------+-----------------+--------------+----------------+-------------+--------+-------------------+

Images:

Thanks in advance to anyone who helps!


Solution

  • Solved: RTFD

    Turns out I shouldn’t have ignored the fact that only Ubuntu 20 LTS is currently supported. I redeployed with Ubuntu 20.04 instead of Ubuntu 22.04 LTS. Hopefully support is added for Ubuntu 22 soon.