Tag Info

Hot answers tagged

4

OP posted: I've resolved that in this way: after to add the new environment i run these commands: juju sync-tools -e maassvr02 juju bootstrap -e maassvr02 --to node4.maas --debug


4

OP posted: I've seen that in /var/lib/maas/dhcp/dhcpd.leases not all nodes in ready state do have a host block with a static entry. I added one for the IP that I need for the machine in question and run dhclient again. I hope this will stick for now, though the source for the issue remains unknown.


1

I faced this problem recently and I'll post here even if this is a very old question. In may case, the node was already allocated to MAAS, so I first had to de-allocate it (with release()) and then delete it. I used the following commands: sudo maas shell >>> from maasserver.models import Node >>> node = ...


1

MAAS API is two things, first and what I use the most is a webpage. The MAAS API address is the ip address of the computer the MAAS regional controller is on. This webpage allows you to allocate nodes to different users, setup networking, and for the most part configure MAAS settings to make it work correctly. Install MAAS can be done in one of two ways. ...


1

ssh ubuntu@192.168.0.21 This will not work with a MAAS node from my experience. You need to use the FQDN hostname you used to name the MAAS node. If you are having DNS issues it will make this difficult. ping OS-baseVM I am assuming OS-baseVM is the name of the MAAS node you are trying to connect to. If you start getting replies great hit ctrl-c. If ...


1

It is not related to two NICs on Ubuntu 14.04! Using one NIC on MAAS cluster controller below! It works from MAAS cluster controller with wakeonlan the node! user@host:~$ wakeonlan 00:0b:db:78:07:33 Sending magic packet to 255.255.255.255:9 with 00:0b:db:78:07:33 But not with juju bootstrap and the node in Ready status on MAAS! user@host:~$ juju ...



Only top voted, non community-wiki answers of a minimum length are eligible