Japje | can 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 simple | 09:26 |
---|---|---|
Japje | image 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.tgz | 09:27 |
Japje | and now im trying to deploy it with: ~# maas admin machine deploy gh48yd distro_series="custom/debian-10.0.2" | 09:27 |
Japje | but im getting 'custom/debian-10.0.2' is not a valid distro_series. | 09:27 |
Japje | ok, found it, turns out the "custom/" part of the name is not needed when doing the deploy, and just doing distro_series="debian" is sufficient | 09:54 |
roaksoax | Japje: filetype | 12:25 |
roaksoax | Japje: look at the help for filetype | 12:26 |
ivve | anyone 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 |
ivve | worked before upgrade, stopped working post upgrade | 15:51 |
ivve | also the same bootpreplies seem not to reflect updates i do in maas, i.e switching around DNS server, NTP or other | 15:52 |
roaksoax | blake_r: ^^ | 15:52 |
ivve | tried restarting everything, even reboots (well had to try). tried looking into some tables in the DB but can't find anything relevant.. | 15:53 |
ivve | i did the upgrade in the test environment and also tried HA, works without any remarks | 15:53 |
ivve | typical :P | 15:54 |
ivve | purged leases file and dhcpd.conf while restarting dhcp just in case. but they are recreated properly with the issue still present | 15:55 |
blake_r | ivve: so the dhcpd.conf is created and the maas-dhcpd service is running? | 15:58 |
ivve | blake_r: yup | 15:58 |
blake_r | ivve: can you send me a copy of the dhcpd.conf contents? | 15:59 |
ivve | sure | 15:59 |
ivve | blake_r: any particular part you are looking for? | 16:00 |
blake_r | ivve: just that all the appropraite configuration values are correct for the file | 16:00 |
blake_r | ivve: you can pm it to me, if you prefer | 16:02 |
ivve | aye working on it :) | 16:02 |
ivve | blake_r: sending now, i redacted some domains and all hosts, i guess they are not required | 16:08 |
ivve | blake_r: https://pastebin.com/UARxPSDA | 16:14 |
ivve | hastebin seems down or smth | 16:14 |
ivve | so this one had to do | 16:14 |
ivve | blake_r: i guess this one is a bit better http://paste.openstack.org/show/755629/ | 16:16 |
ivve | ill be back a bit later, need to drive home | 16:18 |
humbolt | Hi 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 |
roaksoax | humbolt: it should | 18:43 |
roaksoax | rharper: ^^ | 18:43 |
roaksoax | blake_r: ^^ | 18:43 |
roaksoax | 4/win 6 | 18:54 |
blake_r | humbolt: legacy booting yes, efi will only point to one of the disks, but you can use an efi shell to fallback to the other manually | 18:55 |
rharper | roaksoax: 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 boot | 19:03 |
rharper | for 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 challenge | 19:05 |
ltrager | /boot/efi has to be readable by the UEFI firmware. I think adding Linux software RAID would break that | 20:58 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!