/srv/irclogs.ubuntu.com/2019/08/07/#maas.txt

Japjecan someone help me out a little bit. I've added a custom image (debian-10) and i want to deploy a machine via the cli using the custom image. However it kindly refuses me, and i think im just overlooking something simple09:26
Japjeimage was added with: ~# maas admin boot-resources create name=custom/debian title="debian-10.0.2" architecture=amd64/generic content@=/root/debian-10.0.2.tgz09:27
Japjeand now im trying to deploy it with: ~# maas admin machine deploy gh48yd distro_series="custom/debian-10.0.2"09:27
Japjebut im getting 'custom/debian-10.0.2' is not a valid distro_series.09:27
Japjeok, found it, turns out the "custom/" part of the name is not needed when doing the deploy, and just doing distro_series="debian" is sufficient09:54
roaksoaxJapje: filetype12:25
roaksoaxJapje: look at the help for filetype12:26
ivveanyone else upgraded to maas 2.6.0 and having issues with PXE-E53 no boot filename received? i have two environments, one works other doesn't. tried restarting, removing dhcpd.conf and lease files which seems to correctly indicate to serve a FNAME in the BOOTP request. however dhcpdump shows 90% of the BOOTPREPLY is empty,  FNAME: .15:50
ivveworked before upgrade, stopped working post upgrade15:51
ivvealso the same bootpreplies seem not to reflect updates i do in maas, i.e switching around DNS server, NTP or other15:52
roaksoaxblake_r: ^^15:52
ivvetried restarting everything, even reboots (well had to try). tried looking into some tables in the DB but can't find anything relevant..15:53
ivvei did the upgrade in the test environment and also tried HA, works without any remarks15:53
ivvetypical :P15:54
ivvepurged leases file and dhcpd.conf while restarting dhcp just in case. but they are recreated properly with the issue still present15:55
blake_rivve: so the dhcpd.conf is created and the maas-dhcpd service is running?15:58
ivveblake_r: yup15:58
blake_rivve: can you send me a copy of the dhcpd.conf contents?15:59
ivvesure15:59
ivveblake_r: any particular part you are looking for?16:00
blake_rivve: just that all the appropraite configuration values are correct for the file16:00
blake_rivve: you can pm it to me, if you prefer16:02
ivveaye working on it :)16:02
ivveblake_r: sending now, i redacted some domains and all hosts, i guess they are not required16:08
ivveblake_r: https://pastebin.com/UARxPSDA16:14
ivvehastebin seems down or smth16:14
ivveso this one had to do16:14
ivveblake_r: i guess this one is a bit better http://paste.openstack.org/show/755629/16:16
ivveill be back a bit later, need to drive home16:18
humboltHi there! Does MAAS support bootable RAID1 configuration? I see that I can configure a RAID device, but will the MBR and optional efi boot partition be written to both disks?18:34
roaksoaxhumbolt: it should18:43
roaksoaxrharper: ^^18:43
roaksoaxblake_r: ^^18:43
roaksoax4/win 618:54
blake_rhumbolt: legacy booting yes, efi will only point to one of the disks, but you can use an efi shell to fallback to the other manually18:55
rharperroaksoax: we do support raid1 boot, for efi boot partition, there's no acceptable way that I know of to ensure that /boot/efi is mirrored and in-sync; and grub2 itself I don't think has any raid1 support for setting up a mirror before reading/using; lastly, not sure that efi firmware won't write data to the efi boot partition that won't get clobbered if you did mirror efi boot19:03
rharperfor all cases, we install grub to each device in the raid mirror;  for legacy/mbr this all just works;  for efi, it's an exposure due to the above challenge19:05
ltrager /boot/efi has to be readable by the UEFI firmware. I think adding Linux software RAID would break that20:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!