tosaraja | ok. Just by updating to MAAS 2.9.0 I got rid of that loop of norhing happening. But now i end up with 2 hosts in grub and one passed succesfully. damit | 07:35 |
---|---|---|
danboid | I cannot get a juju controller to successfully deploy any more. I think I've made a mess of my maas network settings | 15:37 |
danboid | I'm thinking it might be a good idea to reset my maas controller settings | 15:38 |
danboid | I deleted a few subnets earlier | 15:38 |
danboid | I don't know what the default set is as I've never done a fresh install of maas | 15:38 |
danboid | Do I need to have at least one ipv6 subnet, even if I'm not using ipv6? | 15:39 |
danboid | I think a better question is | 15:45 |
danboid | Is there a script/command I can run to do a health check of my MAAS controller and its DNS/network config? | 15:45 |
danboid | I have had it working already but DNS (bind) has always been flaky so I've been trying to fix that but now it seems worse | 15:46 |
danboid | So, short of me fully re-installing my maas controller from scratch, is there a quicker way to start over? | 15:47 |
danboid | Ubuntu 18.04 / maas 2.4.2 | 15:48 |
danboid | I keeop on getting | 16:01 |
danboid | ERROR failed to bootstrap model: bootstrap instance started but did not change to Deployed state: instance "e8g7pp" is started but not deployed | 16:01 |
danboid | OK looks like | 16:05 |
danboid | sudo dpkg-reconfigure maas-region-controller | 16:05 |
danboid | Might be worth a shot | 16:05 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!