© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I had two more cases today that seem exactly like this again but looking at the logs it might be that the cluster was not formed correctly and this error is just a consequence of that but the installation script did not catch it soon enough.
The output on the console is:
16:28:32 + sunbeam cluster join --role compute --role control --role storage --token eyJuYW1lIjoib2I
16:28:34 > Checking for host configuration of minimum 4 core and 16G RAM ...
16:28:34 > Checking for presence of Juju ...
16:28:34 > Checking for presence of ssh-keys interface ...
16:28:34 > Checking if user ubuntu is member of group snap_daemon ...
16:28:34 > Checking for ~/.local/share directory ...
16:28:34 > Checking if join token looks valid ...
16:28:34 > Checking if Hypervisor Hostname is same as FQDN ...
16:28:34 > Authenticating with Juju controller ...
16:28:34 > Adding node to Sunbeam cluster ...
16:28:34 > Saving machine user ob76-node5.maas for local usage ...
16:28:41 > Registering machine user ob76-node5.maas using token ...
16:29:27 > Adding machine to Juju model ...
16:29:27 > Updating node info in cluster database ...
16:29:31 > Adding Sunbeam Machine unit to machine(s) ...
16:32:38 > Adding MicroK8S unit to machine ...
16:37:29 > Adding MicroCeph unit to machine ...
16:37:29 > Configuring MicroCeph storage ...
16:38:15 Error: Unable to list disks
16:38:15 DEBUG: execute return code is 1
I'm attaching both logs just in case.