=== frankban|afk is now known as frankban === frankban is now known as frankban|afk === Sagar is now known as Guest73708 [09:58] I have configured custom repo for my MAAS cluster, and want to import custom kernel into the MAAS custom repo. Does someone know of tools through which image can be imported? Does it need GPG signing? Any steps on how it needs to be configured? [09:58] posting it again, since I didn't get any response earlier [09:59] just checking if some folks are still active [11:06] Bug #1716894 opened: When trying to enable DHCP on a vlan with unmanaged subnets the message is confusing === frankban|afk is now known as frankban [12:22] Guest73708: custom kernels are not supported in MAAS, so dunno whether it would work well for you. But typucally, if you point to a image mirror, then you dont need new gpgp syncing [12:22] Guest73708: you could try pointing to the index.json, but obviously your images wont be verified [12:28] #roaksoax: well, I am not sure what you mean by pointing to index.json file? [12:28] using simplestreams I created a mirror image [12:29] and now want to add my image into the local mirror repo [12:29] I thought that was the use of custom repo, otherwise, I don't see any significant use of a custom repo [12:30] just having local copy is fine, but real value addition would be if we can add custom images as well [12:30] I can try signing my images as well if required [12:38] Guest73708: the streams will have a index.json, which is not signed, which you could point maas at [12:39] Guest73708: the local mirror of images is to deal with offline environments where maas doesn't have access to the internet [12:41] Guest73708: that said, you upload your own custom images to maas though [12:43] through? [12:48] Guest73708: maas admin boot-resources name=custom/your-ubuntu arch=amd64 content@=/your/custom/image filetype=tgz [12:48] Guest73708: for example [13:18] roaksoax: that is importing complete image. Probably I do not want to go that route. [15:55] morning all :-) === frankban is now known as frankban|afk [16:40] jamesbenson: morning! [16:46] morning, it looks like deployment still fails with GPT on drives still greater than 2TB [16:47] I'm trying on a different R710 to verify, but looks like it gives me the same errors [16:48] roaksoax: ^ [17:00] jamesbenson: it seems that we'll hav eto investigate [17:00] jamesbenson: do you have a installation log to see the failure ? [17:01] I can pull them, where are they? [17:06] I'm hoping it isn't this bug: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1284196 [17:47] jamesbenson: you can grab the UI , on the machine details page there should be "Installation log" or something [17:47] along the lines [17:47] jamesbenson: you usnig 2.2.2 right ? [18:15] roaksoax: yes I am. https://pastebin.com/4YdiSBmF [18:18] roaksoax: also my "trick" of manually creating the 3 partitions, didn't work. Still facing a "attempt to read or write outside of disk 'hd0' Entering rescue mode..." error === med_ is now known as med === med is now known as Guest20317 === Guest20317 is now known as med_ [19:03] roaksoax: thoughts? [19:05] jamesbenson: strange, your pastebin shows as it deployed correctly [19:05] but on reboot, grub didn't boot onto the disk ? [19:13] nope, I get the error mentioned above. [19:14] This is on all of my machines over 2TB [19:22] jamesbenson: right, when does that error happen ? [19:23] after installation is complete and it reboots [19:23] upon reboot it goes straight into that [19:23] did you want me to record again? [19:23] I can show you the whole process if you want [19:25] jamesbenson: ok, this is legacy mode right ? [19:25] jamesbenson: i mean, machines are booting in legacy, not EFI [19:25] yes, bios, not uefi [19:26] jamesbenson: ok, so, how many disks do you hav ein that machine ? [19:26] I have 6 disks but they go through our perc6/i raid controller [19:27] as raid 6, so maas only see's 1 HD [19:27] each drive is 2tb [19:27] individually [19:29] roaksoax: ^^ [19:35] jamesbenson: and, is the bios boot order configured in a way that it would boot off a single specific disk ? [19:35] no, boots only from pxe [19:35] pxe controls if it goes to disk or not [19:43] want me to try with uefi? [19:47] roaksoax: ^^ [19:53] roaksoax: attempting with uefi.... [19:56] jamesbenson: right, but after maas installation, the machine reboots, it will pxe, and it will be told to localboot, and it could be attempting to localboot from a different disk from where the OS has been installed [19:56] I don't think so, maas and raid both tell it there is only 1 disk [19:57] roaksoax: I've manually installed ubuntu before and it also only detects 1 disk in this situation [19:58] jamesbenson: yup, that's what i would have expected as well [19:58] roaksoax: so in that regard all information is consistent. [20:03] jamesbenson: did it work with efi ? [20:04] roaksoax: just finishing now [20:08] roaksoax: failed. https://pastebin.com/6SkfYmFj [20:11] jamesbenson: please file a bug against both 'maas' & 'curtin', attach the installation log [20:11] jamesbenson: and the output of: maas machine get-curtin-config [20:11] jamesbenson: also, there's recetnly been a grub upgrade that could or may be the culprit of this [20:12] roaksoax: Summary: bios/efi maas deployment failure with drives over 2TB? [20:16] jamesbenson: yup [20:21] roaksoax : How do I put this bug against both maas and curtin? [20:21] tags? [20:30] jamesbenson: just file it against MAAS< I'll deal with adding curtin to it [20:30] :) [20:31] lol okay, sorry [20:33] jamesbenson: there's some button there that says "add project" [20:33] actually [20:33] "also affects projecT" [20:33] having issue finding the system-id of this machine... [20:33] it doesn't like the name I gave it. [20:34] jamesbenson: it should be in the URL [20:34] gotcha [20:34] thanks [20:36] should I modify the token & token_secret? [20:37] jamesbenson: nah, those get automatically generated so I dont think you would, but go ahead jus in case :) [20:43] roaksoax: https://bugs.launchpad.net/curtin/+bug/1717031 [20:51] jamesbenson: thanks! [20:51] Bug #1717031 opened: bios/efi maas deployment failure with drives over 2TB [20:52] roaksoax: my pleasure! I hope this can get fixed quickly. I'm going to have to roll back until we can actually deploy. :-( [20:53] jamesbenson: it doesn't work even with your paritioning ? [20:53] i wonder if this is a grub issue [20:54] roaksoax: no it doesn't [20:57] roaksoax: again worked under 2.1.5 though [20:57] with my partitioning and bios [21:12] jamesbenson: same verion of image s? [21:12] yes