[02:27] <benlake> guess I’ll answer my own question. Apparently the HTTP proxy plays a part in the IPMI discovery. Opened TCP 8000 and enlistment was able to determine the power type to be IPMI 2.0
[02:29] <pmatulis> that's very odd
[02:29] <benlake> trial and error got me there.
[02:29] <pmatulis> roaksoax, possible? ^^
[02:29] <benlake> but I suppose my trials could have had an error :D
[02:30] <benlake> watched dropped packets on MAAS, opened things up until enlistement revealed the power type as it had with no firewall
[05:41] <BjornT> benlake: maas installs the ipmitool package on the machine. if it can't use the http proxy, it can't install that package, and thus not determine the power type.
[08:12] <cnf> morning
[08:47] <BjornT> good morning cnf
[08:47] <cnf> \o
[09:51] <sachi> Hi All
[09:51] <sachi> i am using maas 1.9 version
[09:52] <sachi> is there support to deploy 16.04 for any provision
[13:23] <roaksoax>  /win 6
[13:36] <benlake> BjornT: ah, that makes sense.
[13:52] <roaksoax> sanjay: you can deploy 16.04 with 1.9
[13:52] <roaksoax> sanjay: you cannot commission with 16.04 in 1.9
[14:11] <sanjay> i have mass 2.1.5
[14:11] <sanjay>  I can commission nodes
[14:12] <sanjay> but while deploying at last moment its shows error of grub rescue>
[14:12] <sanjay> node is at final stage to get delpoyed but if grub rescue doesnt come
[14:14] <roaksoax> sanjay: that seems like a deployment failure
[14:14] <roaksoax> sanjay: grab the installation log from the UI
[14:14] <roaksoax> on the node that failed
[14:14] <roaksoax> go to the bootom part
[14:14] <roaksoax> where the machine output is
[14:14] <roaksoax> and on the dropdown select installation log
[14:14] <roaksoax> and pastebin that
[14:16] <sanjay> error: attempt to read or write outside of disk 'hd0'
[14:20] <roaksoax> sanjay: can you pastebin it all please ?
[14:20] <sanjay> i can see the outputsummary logs from webui
[14:21] <sanjay> how to use pastebin
[14:23] <sanjay> https://pastebin.com/xWCE4PYT
[14:24] <roaksoax> sanjay: on the dropdown menu, what options do you have on that sectio n?
[15:10] <mup> Bug #1693255 opened: [2.2, UI] Cannot add an interface when the machine is "NEW' <MAAS:New> <https://launchpad.net/bugs/1693255>
[15:10] <mup> Bug #1693256 opened: [2.2, UI] Cannot add an interface when the machine is "NEW' <MAAS:Triaged> <https://launchpad.net/bugs/1693256>
[15:27] <xygnal> after setting boot disk for a machine in maas
[15:27] <xygnal> how do I apply that?  the machine still shows sda as the boot disk, even though I got a 200 back from the API :/
[15:29] <xygnal> well let me put it this way, it still shows up as the install disk in the storage tab.  do I need to combine boot disk with something else to change the install disk?
[15:35] <benlake> I’m very new to MAAS, but I get the impression any changes such as the one you speak are Deploy time implemented only.
[15:36] <benlake> I don’t think it is designed to make changes post deploy
[15:37] <sanjay> one more thing
[15:38] <sanjay> does we need to have atleast 2 disks on server
[15:38] <sanjay> or with 1 disk also OS can be deployed
[15:42] <benlake> one disk is fine. what is your thinking around needing 2 disks?
[15:58] <sanjay> no just asking
[15:58] <sanjay> do we need to do any partition
[15:58] <sanjay> it creates on GPT partition and other part-2 partion with full disk
[16:06] <kiko> if you are using EFI, yes
[16:22] <benlake> sanjay: before you deploy, you can mess with the partitioning scheme on the node
[16:23] <benlake> unfortunately there doesn’t appear to be a way to save that scheme and apply it to other machines. I assume this isn’t a new thought and someone is thinking about custom layouts, eventually.
[16:39] <kiko> benlake, we're working on that right now in fact
[16:39] <kiko> the first iteration will be a dump-to-yaml and upload-yaml
[16:40] <benlake> look at that, heroes of the people
[16:40] <benlake> that’s a good start
[16:40] <benlake> removes all the UI work
[16:42] <kiko> we are also doing something interesting for our use case, which is grouping machines into buckets of "identical" config
[16:42] <kiko> so you'll be able to easily configure a set of machines with the same layout
[16:42] <kiko> and by identical config, layout I mean # and type of NICs, drives, and cpu/core and RAM count
[16:45] <cnf> kiko: accepted :P
[16:45] <kiko> thanks!
[16:46] <cnf> :P
[17:11] <mup> Bug #1693299 opened: MAAS allows any image name to be uploaded by only known images can be deployed <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1693299>
[17:17] <mup> Bug #1693299 changed: MAAS allows any image name to be uploaded by only known images can be deployed <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1693299>
[17:20] <mup> Bug #1693299 opened: MAAS allows any image name to be uploaded by only known images can be deployed <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1693299>
[17:25] <sanjay> Guys i have deployed 4 nodes..i created one /boot partition and other / root partition and started deployed and it worked for me
[17:25] <sanjay> thanks all for your support
[17:26] <sanjay> hope this can be helpful to other people who are facing same error
[17:27] <benlake> kiko: +1 to identical layouts
[17:27] <kiko> benlake, thanks -- I think it's going to be really useful
[17:28] <ThiagoCMC> hey guys, is it possible, via MaaS -> Interfaces, to create OpenvSwitch Bridges? And not only Linux Bridges...?
[17:48] <pmatulis> kiko, i think this is also on the map but, to be sure, please allow (storage) percentages when changing a layout
[17:52] <pmatulis> currently sizes need to be in, gulp, bytes
[17:57] <kiko> pmatulis, yes indeed
[17:57] <kiko> ThiagoCMC, not currently
[17:57] <ThiagoCMC> Hmm... Ok!
[18:04] <sanjay> does anyone can give exact layout in % wise when doing partition manually
[18:12] <maticue> Hi everyone! I see that maas region controller and maas rack controller DNS registers are under ".maas" domain. Is is possible to change these domains? Can be different for rack controller and region controller? Finally, could some one guide me and tell me how to change this?
[18:20] <maticue> nobody?
[18:24] <ThiagoCMC> you can add more domains
[18:24] <ThiagoCMC> and move the nodes to it, before deploying
[18:30] <sanjay> Mass dhcp not running
[18:30] <sanjay> can anyone please let me know how to start it
[18:46] <ThiagoCMC> reboot
[18:46] <ThiagoCMC> =P
[18:53] <maticue> ThiagoCMC: I created more domains , I also deployed new servers and I know how to assign them to the new domains. However, I can't do this with maas rack controller and maas region controller
[19:18] <xygnal> roaksoax: seems root_disk is ignored on custom image?
[19:22] <roaksoax> benlake: https://bugs.launchpad.net/maas/+bug/1418044/comments/3 -> in your comment there, what version of MAAS are you using? What was set in /etc/maas/regiond.conf and what was set in /etc/maas/rackd.conf ?
[19:23] <roaksoax> xygnal what is the custom image you are trying to deploy ?
[19:47] <xygnal> a centos7 cloud image we have made some tweaks on
[20:30] <ThiagoCMC> Guys, at the end of a deployment, I'm seeing the following message: "cloud-init[XXXX]: Can not apply stage final, no datasource found!"
[20:30] <ThiagoCMC> What to do?
[20:31] <ThiagoCMC> I'm running MaaS Next
[20:31] <ThiagoCMC> It was working this morning but, I updated the box because a new package appeared on MaaS Next PPA...
[20:31] <roaksoax> xygnal: at the moment we dont support any storage config for centos, I think that's the culprit.
[20:32] <roaksoax> xygnal: you could customize the image curtin hooks to install where you need them to
[20:32] <roaksoax> ThiagoCMC: has it caused a failed deployment ?
[20:32] <ThiagoCMC> I was stucked...
[20:32] <ThiagoCMC> I rebooted the node, boom! It worked!
[20:33] <roaksoax> ThiagoCMC: strange, it would be interesting to see the full cloud-init log if you can grab that
[20:33] <ThiagoCMC> Sure, I'll collect it and post on pastebin
[20:33] <roaksoax> ThiagoCMC: but final has had tiny bug fixes not at all related to metadata server or anything of the sorts
[20:33] <ThiagoCMC> Hmm... I see
[20:33] <ThiagoCMC> which file should I collect?
[20:34] <roaksoax> ThiagoCMC: /var/log/cloud-init*.log from the ephemeral env if you can, and also /var/log/maas/regiond.log and maas.log
[20:34] <ThiagoCMC> ok
[20:47] <ThiagoCMC> roaksoax, figured out! For some reason, MaaS picked up the wrong subnet for a fabric... So, it gave two IPs from the same subnet, to two different segments, which was causing problems with the communication between cloud-init and the metadata server.
[20:49] <xygnal> roaxsoak: is that neccesary? can customs or centos not use root_device?
[20:50] <xygnal> roaxsoak ok i see.  any example code?
[21:23] <xygnal> roaxsoax: going to need a little more info on using curtain
[21:24] <xygnal> roaxsoax: for that purpose
[21:26] <xygnal> using block-meta?
[21:29] <roaksoax> xygnal: so IIRC< curtin will pick up the first device it finds in the list
[21:29] <mup> Bug #1693358 opened: VLAN name mismatch between web UI and API <MAAS:New> <https://launchpad.net/bugs/1693358>
[21:30] <roaksoax> xygnal: and on the OS' where we dont configure the underlying store, like centos, we dont pass along any storage config because that could actually break the deployment of things
[21:31] <xygnal> do i neee to pre-label it so it knows to pick it up?
[21:31] <xygnal> label=root or such?
[21:32] <roaksoax> xygnal: i need to step out right now. I'll try to come back later, but otherwise we can pick that up tomorrow
[21:34] <xygnal> ok.
[22:00] <xygnal> where does my curtin_userdata_custom need to be, region or rack server?
[23:29] <mup> Bug # changed: 1687420, 1688060, 1689288, 1689838, 1690144