[04:35] <mup> Bug #1698891 changed: [web UI] non-admin can appear to create logical volume <docteam> <MAAS:Expired> <https://launchpad.net/bugs/1698891>
[04:35] <mup> Bug #1702919 changed: displayed lease IP information not updated when entering rescue mode <dhcp> <MAAS:Expired> <https://launchpad.net/bugs/1702919>
[08:50] <mup> Bug #1715337 opened: [2.3a2] Missing DNS in rescue mode <MAAS:New> <https://launchpad.net/bugs/1715337>
[09:20] <mup> Bug #1715338 opened: Dumpdata failing for table metadataserver.nodeuserdata <MAAS:New> <https://launchpad.net/bugs/1715338>
[09:50] <mup> Bug #1715345 opened: [2.3 alpha 2, Machine details] When I click the edit button, the Save and Cancel buttons remain hidden <ui> <MAAS:New> <https://launchpad.net/bugs/1715345>
[10:20] <mup> Bug #1715353 opened: [2.3 alpha 3, Subnets/VLAN details] VLAN details do not have the Edit button and can still be edited with auto-save <ui> <MAAS:New> <https://launchpad.net/bugs/1715353>
[10:34] <c06> hi all i am trying test in my vbox VM
[10:35] <c06> i have two vm one VM with public and hostonly adapter(192.168.56.101 - gw 192.168.56.1), and i installed maas
[10:36] <c06> i configured second VM with hostonly adapter(192.168.56.102). but MAAS is unable to find the second machine. any suggestions.??
[10:37] <c06> Also in my second machine i enabled Network(boot) PXE
[10:53] <c06> anyone on.?
[11:35] <c06> my node is unable to get the boot on tftp server
[11:49] <c06> it got ip but after we are getting "No bootable medium found."
[14:51] <roaksoax> cnf: did you enable dhcp and/or imported image s?
[14:51] <roaksoax> err
[14:51] <roaksoax> sory
[14:54] <cnf> Hmm?
[14:54] <cnf> I'm in the US on holiday atm
[15:00] <cnf> roaksoax:  so hi from carson city \o :P
[15:25] <roaksoax> cnf: sorry my message was for someone else
[15:59] <ybaumy> roaksoax: i know you are not in charge fixing that damn resolv.conf problem. but do you have a estimate on how long it will be until we get a solution. i would really need maas atm. i tried foreman but its not compatible with juju
[16:00] <ybaumy> i also tried 14.04 for commissioning
[16:00] <ybaumy> but its the same problem
[16:00] <ybaumy> and in the end juju doesnt work too
[17:39] <xygnal> roaksoax: get a chance to see my paste?
[17:41] <xygnal> roaksoax: not sure if this is an existing bug. cannot find one.
[17:53] <jamesbenson> can someone destribe badblocks-destructive further?  I've read the info on the release notes... just not sure what exactly it does.... i.e. are the hard drives erased?  just bad sectors?
[18:05] <xygnal> i assume destructive mode does read AND write testing
[18:06] <xygnal> write testing being destructive
[18:44] <jamesbenson> yeah, I'm was guessing that any bad sectors they find, they mark bad so any data there is unrecoverable...
[18:44] <jamesbenson> good to get validation.  thank you xygnal
[18:45] <jamesbenson> do any of the tests work when they have a raid controller card?
[18:46] <jamesbenson> the few tests I've ran, they all seem to fail (have a perc 6i raid card)
[20:08] <xygnal> not sure James. dev team seems busy today. still waiting on a reply myself before submitting a bug.
[22:03] <mup> Bug #1715501 opened: MAAS can't connect to RSD 2.1 pod <MAAS:New> <https://launchpad.net/bugs/1715501>
[22:09] <mup> Bug #1715501 changed: MAAS can't connect to RSD 2.1 pod <MAAS:New> <https://launchpad.net/bugs/1715501>
[22:12] <mup> Bug #1715501 opened: MAAS can't connect to RSD 2.1 pod <MAAS:New> <https://launchpad.net/bugs/1715501>