[00:32] <greenride> I setup one maas cluster, which has 1 node. I have a total of two machines. I turned on PXE-boot and wake-on-lan in the BIOS for that node.When I select commission selected nodes, I get the error message: "The action 'commission selected nodes' could not be performed on 1 node because its state does not allow that action."
[00:33] <greenride> How should I diagnose this problem?
[00:44] <greenride> I tested that the following two commands wakeup the node: 'sudo etherwake <my_mac>' and 'wakeonlan <my_mac>'. However, selecting commission does not wakeup the node.
[00:47] <h0mer> did you install etherwake?
[00:47] <h0mer> apt-get install etherwake
[00:47] <greenride> h0mer: I installed both wakeonlan and etherwake.
[00:49] <greenride> wakeonlan works from both my laptop and the maas controller server.
[00:49] <greenride> etherwake works from my laptop but not the maas controller server.
[00:50] <h0mer> if you machine on a different subnet?
[00:50] <greenride> I get the error message: 'SIOCGIFHWADDR on eth0 failed: No such device'
[00:51] <greenride> Both the laptop and maas controller node are on the same subnet: 192.168.3.xxx.
[00:52] <greenride> Both using Ubuntu 14.04 LTS. One is desktop and other is server.
[00:55] <greenride> Maybe I should ask on Ubuntu about the etherwake before proceeding with the commissioning of nodes. If both etherwake and wakeonlan are available on the maas controller server, which does it attempt to use?
[00:58] <h0mer> reboot the maas node
[00:58] <h0mer> it uses one or the other
[00:58] <h0mer> the script in the /etc/maas templates directory checks to see wheich one you have installed
[00:59] <h0mer> if you have both, i think it uses etherwake first
[01:13] <lathiat> one thing i had to do greenride was manually set the mac for wakeonlan on each ndoe
[01:13] <lathiat> it wouldn't pick it up from its general info
[01:13] <lathiat> not sure if that helps
[01:20] <greenride> lathiat: 'sudo etherwake <my_mac>' works perfectly from my laptop, but it doesn't work from the mass controller server. So, the target machine is setup properly. So is my laptop. It's the maas controller box that has a problem.
[01:21] <h0mer> after installing etherwake/wakeonlan, i had to reconfigure maas
[01:21] <h0mer> basically bring it down and back up
[01:21] <h0mer> (i rebooted the node)
[01:21] <h0mer> and my hp machiens with wol worked after that
[01:24] <lathiat> greenride: i mean within the maas config
[01:25] <lathiat> greenride: but if "sudo etherwake" (literally) doesn't work, then yeah
[01:25] <lathiat> i also had problems with it working over a vlan interface
[01:25] <lathiat> so i had to stop making my maas vlan an ethernet trunk
[01:25] <lathiat> i suspect that was a switch issue but i didn't verify that fully
[01:28] <h0mer> if maas is on another subnet, then you'd need to add the subnet prefix to the etherwake/wakeonlan config
[01:35] <h0mer> greenride: can you do a wol or etherwake from the maas node to wake up your machine?
[01:56] <greenride> h0mer: laptop ip: 192.168.3.219, router: 192.168.3.1, maas controller: 192.168.3.174, maas node: 192.168.3.131
[01:57] <h0mer> can you use wol or etherwake from the maas controller (command line) to turn on the machine?
[01:58] <greenride> h0mer: wakeonlan <mass_node_mac_address> from the maas controller command line works.
[01:58] <h0mer> but maas can't wake up the machine from the gui?
[01:59] <greenride> h0mer: 'sudo etherwake <mass_node_mac_address>' does not work.
[01:59] <greenride> h0mer: That's right. From the GUI, it does not wakeup the maas node.
[02:03] <h0mer> is wake on lan installed in the /usr/sbin directory?
[02:03] <h0mer> i mean /usr/bin
[02:03] <greenride> That's correct. wakeonlan is in /usr/bin. etherwake is in /usr/sbin.
[02:04] <h0mer> you've rebooted maas?
[02:04] <h0mer> or the maas node
[02:04] <h0mer> that is?
[02:05] <greenride> The maas node is in the power off state when the command is executed. I've tried this multiple times from the different machines/different commands.
[02:05] <h0mer> no i mean reboot the machine maas is on
[02:05] <greenride> The maas controller node?
[02:05] <h0mer> yes
[02:05] <greenride> Let me try that.
[02:06] <h0mer> and then when maas comes back up, delete the node in the maas gui
[02:06] <h0mer> and re-add it using wol credentials
[02:06] <h0mer> i mean wol mac address
[02:06] <greenride> Before deleting, should I try the etherwake command?
[02:07] <h0mer> you mean from cli?
[02:07] <greenride> yes
[02:07] <h0mer> i thoguht you said that worked?
[02:08] <greenride> h0mer: wakeonlan <mac_address> works. sudo etherwake <mac_address> does not.
[02:08] <h0mer> shouldn't matter, just looked at the template script and WOL is used first, then etherwake
[02:08] <greenride> one command works from the maas controller node. The other command does not work from the maas controller node.
[02:09] <greenride> From my laptop, both commands work.
[02:09] <greenride> Then, let me delete and re-add the node.
[02:09] <h0mer> rgr
[02:09] <greenride> rgr?
[02:10] <h0mer> roger
[02:10] <h0mer> as in okay.
[02:10] <greenride> Understood the 'roger'... the abbreviation I didn't. :)
[02:10] <h0mer> rgr
[02:12] <h0mer> and btw do you have two nic's connected on the maas controlelr node?
[02:13] <greenride> No. Only one nic.
[02:14] <h0mer> alright, the only other thing i can think of is a tcp/udp issue.  I know wol uses tcp and i think etherwake uses udp
[02:14] <greenride> By the way, it worked this time. After adding the node, status became 'Commissioning' and it booted.
[02:14] <h0mer> rgr
[02:14] <greenride> dhcp didn't work. But, the boot part did.
[02:14] <h0mer> last time i had this issue, i just rebooted the maas controller node after installing etherwake
[02:15] <h0mer> whats the dhcp stuff you're talkinga bout?
[02:16] <greenride> After the wake on lan, the maas node tries to get an ip address using DHCP. That fails.
[02:16] <greenride> In the PXEBoot process.
[02:17] <h0mer> but the wol/etherwake stuff works now right?
[02:17] <greenride> Yes, it does.
[02:17] <greenride> Thanks for your help.
[02:18] <h0mer> alright, is maas now setup to manage the DHCP and DNS on you network?
[02:18] <greenride> Deleting the node and re-adding it did the trick.
[02:18] <greenride> h0mer: No. The DHCP is done through the router. The router runs OpenWRT.
[02:19] <h0mer> did you set up the network in maas to point to the router?
[02:19] <greenride> The OpenWRT router has dnsmasq.
[02:19] <greenride> h0mer: No. I didn't
[02:19] <h0mer> and it's set to pxelinux.0 and then points to the maas controller node?
[02:19] <h0mer> goto the networks tab and configure the gateway and router ip to point to the DHCP server (in maas)
[02:20] <greenride> No, the only thing I did was add 'next-server <maas_controller_ip>' to the dnsmasq section of /etc/config/dhcp on the OpenWRT router.
[02:20] <greenride> rgr
[02:20] <h0mer> oh the stuff i told you earlier?
[02:20] <h0mer> got it
[02:20] <greenride> right
[02:21] <h0mer> id need to see how you set up the network in maas
[02:21] <h0mer> is it managed or unmanaged?
[02:22] <greenride> No networks are defined.
[02:22] <h0mer> the networks tab shows no networks?
[02:22] <greenride> Right.
[02:22] <greenride> That's my problem I believe. :)
[02:22] <h0mer> goto the maas controller and type 'ifconfig'
[02:23] <h0mer> does it show eth0 or eth1 or something along those lines?
[02:23] <greenride> It shows lo and p4p1. p4p1 is assigned the ipv4 address 192.168.3.174.
[02:24] <h0mer> is this a vm?
[02:24] <greenride> No
[02:24] <greenride> Physical box.
[02:24] <h0mer> goto the networks tab and add a network
[02:26] <h0mer> set the gateway and dns server to your dhcp server ip
[02:27] <h0mer> then goto clusters tab
[02:27] <h0mer> and then add an interface
[02:27] <h0mer> p4p1 or whatever
[02:27] <h0mer> do the same thing, but set it as "unmanaged"
[02:27] <h0mer> set everything up to the router IP
[02:27] <h0mer> and then leave all the dhcp/staic fields empty
[02:28] <h0mer> then delete your node from maas and re-enlist it
[02:28] <greenride> In the network tab for 'add a network', only fields for name, description, ip, netmask, vlan tag, and connected network interface cards exist.
[02:29] <greenride> There is no field for gateway or dns server.
[02:30] <h0mer> theres no field that says "default gateway" or "dns servers'?
[02:30] <h0mer> what version of maas are you running?
[02:30] <greenride> Right.
[02:30] <h0mer> (it's on the bottom of the page)
[02:31] <greenride> The version that installs by default with Ubuntu 14.04.2 LTS.
[02:31] <h0mer> what does it say on the bottom of the maas page?
[02:32] <greenride> © 2012 Canonical Ltd. Ubuntu and Canonical are registered           trademarks of Canonical Ltd.           View Documentation
[02:32] <h0mer> sounds like a pretty old version
[02:33] <h0mer> can you answer your pm?
[02:33] <greenride> answer your pm?
[02:33] <greenride> What do you mean?
[02:33] <greenride> I'm trying to find the version.
[02:33] <h0mer> do you not see a pm from me?
[07:31] <greenride> h0mer: I got maas fully installed. I'm playing around with it. Thanks for your help.
[09:18] <haripriya> I am facing an issue, Installed MAAS in a vagrant box using virtual box as provider. On accessing the web UI, I can see only the nodes links and no images/ cluster links are available. I tried the sudo maas-import-pxe-files but still the issue persists
[09:18] <haripriya> The nodes created were all stuck in commissioning status. Can anyone help me? A
[09:48] <h0mer> @haripriya: not sure I understand your issue.  Is the gui not resolving the links for the pages, or are you having a commissioning problem? or both?
[09:55] <haripriya> I am having both the issues
[09:55] <haripriya> gui is showing only the nodes link
[09:56] <haripriya> and after adding nodes, they will stuck in commisioning status
[22:59] <greenride> h0mer: Thanks for your help yesterday. I got maas up and running.
[23:13] <h0mer> np