[04:25] <mup> Bug #1611481 changed: IPMI autoconfiguration and startup not working <MAAS:Expired> <https://launchpad.net/bugs/1611481>
[04:25] <mup> Bug #1611980 changed: Upgrade from MAAS 2.0 RC3 to RC4 has pre-removal script error messages <MAAS:Expired> <https://launchpad.net/bugs/1611980>
[04:56] <Prabakaran> Hello Team, Getting timeout issue while commissioning the node in MAAS 1.9, Logs are pasted in here  http://pastebin.ubuntu.com/23301741/ could somebody help me on this?
[10:56] <mup> Bug #1631908 opened: VLAN over balance bondig doesn't work <MAAS:New> <https://launchpad.net/bugs/1631908>
[12:17] <mup> Bug #1631934 opened: MTU values should not be on the bridged interface <MAAS:New> <https://launchpad.net/bugs/1631934>
[13:26] <mup> Bug #1631946 opened: daily images have broken cloud-init <MAAS:Incomplete> <https://launchpad.net/bugs/1631946>
[14:26] <mup> Bug # changed: 1274168, 1279460, 1326485, 1363074, 1364097, 1367843, 1368307, 1370371, 1372794, 1374242, 1376075, 1378865, 1379639, 1381390, 1622971
[14:26] <mup> Bug #1631971 opened: TestDHCPNetworkLayout.test__dhcp_configurations_rendered is dependent on /etc/hosts <ipv6> <tests> <MAAS:Triaged> <https://launchpad.net/bugs/1631971>
[14:56] <mup> Bug # changed: 1272016, 1343317, 1374478, 1393997, 1394277, 1402086, 1437251, 1438780, 1453749, 1465735, 1467694, 1476254, 1476746, 1481281, 1481283, 1483694, 1498854, 1503483, 1503530, 1507670, 1510070, 1513695, 1515975, 1519177, 1526859, 1556431, 1590768
[15:18] <mup> Bug #1628114 changed: [FUJ] SSH input field not indicated for invalid username & the error is incomprehensible <MAAS:Fix Released> <https://launchpad.net/bugs/1628114>
[15:18] <mup> Bug #1629080 changed: [2.1 ipv6] deploying machine needs connectivity to maas (address family) <maas-ipv6> <MAAS:New> <https://launchpad.net/bugs/1629080>
[15:36] <mup> Bug #1621090 changed: rack controller broken after a period of time when deployed on a seperate machine from the region <MAAS:Invalid> <https://launchpad.net/bugs/1621090>
[16:52] <Prabakaran> Hello Team, Getting timeout issue while commissioning the node in MAAS 1.9, Logs are pasted in here  http://pastebin.ubuntu.com/23301741/ could somebody help me on this?
[16:57] <mup> Bug #1514436 changed: Support redirects for maas.ubuntu.com/images <MAAS:Fix Released by andreserl> <https://launchpad.net/bugs/1514436>
[18:54] <baldpope> sup all - am I correct in understanding that maas cannot deploy to a vm running on the free version of esxi?
[18:55] <baldpope> when attempting, I get a generic error - Unable to find a rack controller with access to chassis
[18:56] <baldpope> i get that when running that from cli or webui when attempting to add chassis
[18:57] <baldpope> and if I attempt to add a machine, i get this error in the webui -No rack controllers can access the BMC of node:
[19:00] <roaksoax> baldpope: maas *can* deploy to a VM running on ESXI
[19:01] <roaksoax> baldpope: the issue, based on what you mention, is that the rack controller cannot access the ESXI host IP
[19:01] <baldpope> definitely not a firewall issue this time - no blocked traffic between the two
[19:01] <roaksoax> baldpope: for example, you may not have routing between MAAS and the ESXi host you are trying to control
[19:02] <roaksoax> baldpope: can you ping your ESXi host from the machine MAAS is running ?
[19:02] <baldpope> i can run openssl s_client -connect against the vm server and do showcerts
[19:02] <baldpope> yea, ping works as well
[19:02] <roaksoax> baldpope: is the rack controller connect to MAAS ?
[19:03] <roaksoax> baldpope: as it, it is showing a green check that everything is working ?
[19:03] <baldpope> roaksoax, not sure I know where to look for that
[19:04] <roaksoax> baldpope: in the UI, under the 'Nodes' tab, click on 'Controllers'
[19:04] <baldpope> yea, green
[19:05] <roaksoax> baldpope: strange then
[19:05] <roaksoax> baldpope: so do this: tail -f /var/log/maas/rack.log and then add a chassis, grab the log it shows, and please file a bug :)
[19:05] <roaksoax> baldpope: also, provide output pingin the IP where ESXi host is running and such
[19:10] <baldpope> roaksoax, if I do attempt to add chassis, supplying the hostname, user/pass and prefix filter, I receive the following in the webui
[19:10] <baldpope> Unable to find a rack controller with access to chassis <myhost>
[19:10] <baldpope> but I see no output in rackd.log
[19:15] <roaksoax> baldpope: what if you supply an IP instead of a hostname ?
[19:15] <baldpope> tried both, same
[19:18] <baldpope> I can kinda proceed if I set the power to manual and then manage power via the UI through vmware
[19:18] <baldpope> was able to complete the commission step
[19:22] <MrDanDan> hi guys
[19:22] <MrDanDan> at the end of the commision phase, the nodes should power off, right?
[19:22] <baldpope> yea
[19:23] <roaksoax> baldpope: if you could file a bug with the logs above would be great
[19:23] <MrDanDan> well, mine enter prompt
[19:23] <baldpope> roaksoax, ok, will give you what I got
[19:23] <MrDanDan> and on web UI hangs at commisioning
[19:23] <roaksoax> MrDanDan: have your machines changed from "Commissioning" to "Ready"  ?
[19:23] <MrDanDan> no
[19:23] <roaksoax> MrDanDan: so then they are probably not accessing the commissioning environment
[19:23] <MrDanDan> they stay commisioned
[19:23] <MrDanDan> well, the network is a host-only on vmware
[19:24] <MrDanDan> if that is of any issue
[19:24] <roaksoax> MrDanDan: either a fail in PXE booting or loading the image, to tring to commission and something blocking it
[19:30] <MrDanDan> think it was the fact the vms had ide disks attached
[19:30] <MrDanDan> trying with scsi
[19:57] <MrDanDan> issue was caused by some networking issues with HDCP
[19:57] <MrDanDan> issue was caused by some networking issues with DHCP
[20:15] <baldpope> roaksoax, https://github.com/conjure-up/conjure-up/issues/484
[20:20] <stokachu> baldpope: yea the charm is attempting to locate a network device that isn't accessible
[20:23] <baldpope> not even sure where to begin with that?
[20:31] <baldpope> stokachu, what if deployment just takes a really long time - i ask because after waiting (for about 10+ mins) on 4 of the 5 blades, I see started lxd - main daemon
[20:32] <baldpope> but the conjure-up session was already dead
[20:32] <baldpope> is it possible to continue or?
[20:33] <stokachu> it'll continue without conjure-up running
[20:33] <stokachu> you'll just need to use juju for interfacing with it
[20:35] <baldpope> juju status shows everything either in a waiting or pending state - nothing appears to have completed
[20:39] <stokachu> neutron-gateway is in a failed state because of the network config
[20:39] <stokachu> so that needs to be resolved first
[20:40] <baldpope> yea, i just read your comment on github (assume that's you) - how is the network config broken, at the moment, all pretty flat with a single vlan
[20:43] <baldpope> or is this more a basic issue like expecting eth[0-x] where my ethernet devices are named something else?
[21:37] <smgoller> hey all, I've got maas set up and running. The maas DNS component seems to register all the machines in a .maas domain by default. This works fine. Machines that are provisioned correctly get the maas dns server as their default resolver. however, there is no 'search maas' line in the resolv.conf. Is there a maas setting that manages this?
[21:38] <smgoller> so for example, I have a host called r01-s02. ping 'r01-s02' fails because it can't resolve the hostname because of no 'search maas' line in resolv.conf
[21:45] <smgoller> Does anyone have any pointers to best practices when it comes to IPMI?
[21:47] <smgoller> What I've been doing up to this point is putting IPMI traffic on a different vlan that is connected to the rack controller. I provide DHCP on that network via the rack controller. However, I'm running into a problem where there seems to be duplicate lease entries or something and I keep getting errors about keys already existing in the database for a given ip address.