[00:12] Hi there.. looking for a little help.. I've just setup a "vanilla" maas server following the instructions here: http://maas.io/get-started... my nodes are connected to IPMI so I reboot into pxe and the node itself seems to get a DHCP response from the maas server and proceeds to start the boot process. but then it gets stuck with: http://169.254.169.254/2009-04-04/meta-data/instance-id' failed. error. [00:13] the error message says "Failed to establish new connection". [00:14] after cloud-init fails out I end up at an ubuntu login screen but I don't see any nodes getting added into maas. [00:46] Bug #1635069 opened: [web UI] subnet settings are dangerously easy to change [03:44] Bug #1635097 opened: Can't assign SSH-Keys to user via maas-cli [03:47] Bug #1635097 changed: Can't assign SSH-Keys to user via maas-cli [03:50] Bug #1635097 opened: Can't assign SSH-Keys to user via maas-cli [04:14] Bug #1635107 opened: maas.power Error changing power state (on) while commissioning the node [04:17] Bug #1635107 changed: maas.power Error changing power state (on) while commissioning the node [04:20] Bug #1635107 opened: maas.power Error changing power state (on) while commissioning the node [05:14] hi , I have setup MAAS(version 1.9) using VM's (ubuntu 14.04). I want to deploy a juju charm on the node having storage disk attached. I have created one called sdb. [05:15] But when i deploy the charm, I see that the status in MAAS UI us Failed Deployment for the node [05:15] I see the below errror in the MAAS install logs [05:15] Installing for i386-pc platform. grub-install : error: unable to identify a filesystem in hostdisk//dev/sdb; safety check cant be performed failed to install grub! Command: ['install-grub', 'tmp/tmpqwTtyG/target', '/dev/sdb]' [05:15] can anyone please help me in debugging this issue [05:23] Hello === Mohit is now known as Guest6607 [14:14] Hi team, I deployed a charm with MAAS as cloud provider, the charm got deployed successfully, but in the installation logs on MAAS console, i see this error message : Error: /dev/sdb: unrecognised disk label [14:14] can anyone please help me on this [15:15] Bug #1635298 opened: Ability to assign deployed MAAS nodes to a "group" or "project" would be helpful === skr is now known as Guest48026 [18:03] Bug #1633468 changed: [Subnets page, DD] Add a warning message when Device discovery is disabled [18:42] Looking for some help. I've setup a new MAAS server and enabled my hosts to network boot (PXE). upon booting, they get a DHCP response from maas and start the "Booting under MAAS..." process.. but I never see the new machine pop up in the MAAS machine list. === plumgrid is now known as Baqar [20:01] swjen, which version? [20:30] Hi brendand. I am running MAAS 2.0.0 [20:35] swjen, what do you see in /var/log/maas/rsyslog/ on the maas server? [20:43] brendend: I don't see anything actually. the directory is empty. [20:43] swjen, not even maas-enlisting-node? [20:44] nope.. completely empty./ [20:48] brendand: if a little backstory helps, All I have done is follow the "quick start" steps here: http://maas.io/get-started. I did notice that the maas server has "maas_region_controller" installed, but it does not have "maas_cluser_controller" installed. from some googling I wasn't sure if this was necessary or not. [21:10] does anyone know if you can set the upstream DNS and NTP for MAAS 2.0 via the maas commandline [21:11] ah, found it [21:34] brendand: are you still here? [21:38] swjen, if you can get console access to the machine you should watch what that's doing. even better if you can copy it somewhere and show us [21:38] it's a bit late for me so i might stop responding [21:42] swjen, try back tomorrow if i don't [21:43] brendand: thanks! I do have IPMI access and have been watching the systems that way.. difficult to copy out stuff during the process but I have taken some screen shots.. basically.. immediately after the PXE boot I see "Booting under MAAS direction..." then a bunch of stuff scrolls across the screen.. then it throws some could-init errors about establishing a new connection.. then it stops at an ubuntu login screen..