[00:00] <mup> Bug #1696276 changed: Comissioning scripts should trigger a hardware reinventory <MAAS:New> <https://launchpad.net/bugs/1696276>
[00:15] <mup> Bug #1696276 opened: Comissioning scripts should trigger a hardware reinventory <MAAS:Incomplete> <https://launchpad.net/bugs/1696276>
[00:54] <mup> Bug #1696285 opened: Machines that fail hardware testing need to be marked broken before they can be recommissioned <MAAS:New> <https://launchpad.net/bugs/1696285>
[01:09] <mup> Bug #1696285 changed: Machines that fail hardware testing need to be marked broken before they can be recommissioned <MAAS:New> <https://launchpad.net/bugs/1696285>
[01:15] <mup> Bug #1696285 opened: Machines that fail hardware testing need to be marked broken before they can be recommissioned <MAAS:New> <https://launchpad.net/bugs/1696285>
[05:43] <cabinet> I'm having some problems getting a node to come up over PXE -- cloud-init says it can't find it's data source. I haven't worked with maas or cloud-init before, but I was wondering if someone could point me at either a way to log into the box to try to debug it from there, or a set of troubleshooting steps to try around this problem
[05:43] <cabinet> I've looked through the documentation I could find, and haven't turned up anything that's helped
[07:05] <cabinet> What about just pointing me at how I can edit the image that is pushed over and executed? I can't find any 'cloudinit' files on the maas machine
[10:46] <mup> Bug # changed: 1416417, 1436531, 1438091, 1451580, 1468757, 1469663, 1506516, 1506517, 1506518, 1506519, 1506520, 1506523, 1506524, 1506525, 1506528, 1506529, 1512297, 1513392, 1513507, 1536092, 1536094, 1536097, 1536099, 1536101, 1536147
[11:07] <mup> Bug # changed: 1536102, 1536104, 1536106, 1536109, 1536122, 1536123, 1536125, 1536132, 1536137, 1536139, 1536142, 1536144, 1536145, 1536146, 1536148, 1536153, 1536157
[11:40] <mup> Bug #1536131 changed: [Node Networking] Change table widths <design> <ui> <MAAS:Invalid by ricgard> <https://launchpad.net/bugs/1536131>
[14:50] <roaksoax> cabinet: /etc/maas/rackd.conf
[14:50] <roaksoax> cabinet: maas_url, ensure it is pointint to an IP the machines can communicate to
[16:22] <mup> Bug #1696485 opened: MAAS dhcp does not offer up multiple domains to search <MAAS:Triaged> <MAAS 2.2:Triaged> <https://launchpad.net/bugs/1696485>
[16:28] <mup> Bug #1696485 changed: MAAS dhcp does not offer up multiple domains to search <MAAS:Triaged> <MAAS 2.2:Triaged> <https://launchpad.net/bugs/1696485>
[16:37] <mup> Bug #1696485 opened: MAAS dhcp does not offer up multiple domains to search <MAAS:Triaged> <MAAS 2.2:Triaged> <https://launchpad.net/bugs/1696485>
[18:16] <mup> Bug #1696512 opened: [2.2] UI: adding a virsh pod immediately commissions existing kvms <MAAS:New> <https://launchpad.net/bugs/1696512>
[21:44] <xygnal> roaksoax: something about syntax in curtin_userdata_custom vs _centos?
[21:45] <xygnal> getting errors after copying my custom over to try a native cos6 image
[22:47] <ltrager> xygnal: In the root of your CentOS tarball you need to include Curtin hooks which finalize the install
[22:47] <ltrager> xygnal: The ones we ship are at http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/files/head:/curtin/
[22:48] <ltrager> xygnal: Those files should be stored in /curtin in the custom CentOS tar.gz
[22:49] <ltrager> xygnal: We are looking into incorporating those hooks directly into Curtin so that won't be necessary in the future.
[22:58] <xygnal> oh i see
[22:58] <xygnal> you dont install curtin
[22:58] <xygnal> on those
[23:21] <ltrager> xygnal: Curtin is what MAAS uses to install any OS. The current version only knows how to install Ubuntu naively. The hooks tell Curtin how to do things like setup grub.
[23:22] <ltrager> xygnal: One other things I forgot to mention you need to have cloud-init installed
[23:23] <ltrager> xygnal: On CentOS 7 you also need to install https://kojipkgs.fedoraproject.org/packages/python-oauth/1.0.1/10.el7/noarch/python-oauth-1.0.1\
[23:23] <ltrager> -10.el7.noarch.rpm
[23:25] <xygnal> ltrager in this case its only a minor exception need for cos6 which is why I am trying to use the included cos6/7 images
[23:25] <xygnal> we already pre-treat out custom cos7 image, i didnt realize the in-maas option ones were not pre-treated.  I'll look at that next.
[23:47] <sanjay> hi