/srv/irclogs.ubuntu.com/2017/12/06/#maas.txt

mupBug #1736626 opened: [2.4] Cannot add device from dashboard <MAAS:Triaged by ack> <https://launchpad.net/bugs/1736626>00:44
mupBug #1729127 changed: storage: No available machine matches constraints <juju:In Progress by ecjones> <maas (Ubuntu):Invalid> <https://launchpad.net/bugs/1729127>05:46
=== frankban|afk is now known as frankban
eriklonrothHello Channel! I'm looking for some kind of installation guide for MAAS to try out as a reference. Is there some well known source for this apart from the official documentation ?11:51
roaksoaxeriklonroth: what type of guide are you looking for ?12:36
roaksoaxhttps://pages.ubuntu.com/install-maas.html?utm_source=Twitter&utm_medium=Social&utm_campaign=MAAS_videos&12:37
mupBug #1711370 changed: MAAS installation from Ubuntu Server ISO failing after 08 Aug 2017 <MAAS:New> <https://launchpad.net/bugs/1711370>12:41
eriklonrothI'm just looking ahead to avoid any obvious problems before I start =)12:53
=== frankban is now known as frankban|afk
=== frankban|afk is now known as frankban
=== frankban is now known as frankban|afk
mupBug #1736767 opened: Manual power won't survive commissioning/deploying <MAAS:New> <https://launchpad.net/bugs/1736767>17:57
JH_I guess it must have been reported already, but I couldn't find any channel logs. But the maas.io https certificate expired this morning.18:00
klj1218looking for some help, new to maas, just installed 2.3.0~beta2. I can deploy ubuntu images, but deploying centos 7 fails. the install completes and reports "Installation finished. No error reported.", but when the system reboots and boots from local disk it doesn't find a bootable disk19:46
klj1218https://www.dropbox.com/s/gec92wgjx41c0od/deploy-centos-log.png?dl=019:47
klj1218https://www.dropbox.com/s/igm7c97zwp7btc4/rpviewer-2.png?dl=019:47
klj1218my systems have 5 disks, 1 ssd and 4 nvme ... if I pull the 4 nvme, the centos install completes and reboots OK19:49
klj1218ubuntu 17.10 install on the same hardware with all disks (5) present works just fine19:49
klj1218trying to find help to debug19:50
andyshinnthe API for POST /api/2.0/machines/{system_id}/ op=deploy has a user_data field (i'm presuming, cloud-init would use this a config source if the user data has a #cloud-config header). is there a way to set user_data in the UI that i have missed? i didn't see any way to do this. i am playing with 2.2 (didn't see this as a feature in 2.3)21:15
roaksoaxandyshinn: no21:50
roaksoaxandyshinn: only available via the API21:50
roaksoaxklj1218: beta2?? you should upgrade to final and re-try21:51
roaksoaxklj1218: we can't support your if you still running beta221:51
roaksoaxgiven that final has a lot of fixes21:51
klj1218roaksoax: I installed MASS from 17.10 media, running apt update says "All packages are up to date."21:54
klj1218roaksoax: where should I pull the updates from?21:55
klj1218roaksoax: I'm guessing this will give me the latest 2.322:03
klj1218roaksoax: sudo add-apt-repository ppa:maas/stable22:03
andyshinnwould the MAAS team entertain a feature request to allow user data to be set in the UI at deploy or configuration time (similar to how you might do with AWS or GCP instances)?22:18
roaksoaxklj1218: yes, the ppa woyuld be good. 2.3 final should be landing in the ubuntu archives soon22:21
roaksoaxandyshinn: such feature request is something we have had discussed before, but not necessarily something that's a priority right now. Although, we do have it in mind22:22
klj1218roaksoax: just updated the system and I'm currently re-running my test22:22
roaksoaxklj1218: sounds good, let me know how it goes22:25
roaksoaxklj1218: also, are you sure the BIOS is set to the correct disk for booting, that could be the issue as well22:25
roaksoaxklj1218: and there's an ongoing discussion over the mailing list22:25
andyshinnok, i didn't see it listed on launchpad bugs. could i create it so it could be followed? i understand it is a low priority / nice to have thing. but being able to track it so i know when / if status changes would be nice22:26
klj1218roaksoax: oh I will :)22:26
klj1218roaksoax: yup, the BIOS doesn't let me set the NVME disk for boot22:26
roaksoaxandyshinn: yeah for sure!22:26
klj1218roaksoax: same failure as before22:27
klj1218roaksoax: after the install, which the logs say finished with error, the system reboot from local disk and fails22:28
klj1218roaksoax: this is the screenshot from the console22:29
klj1218https://www.dropbox.com/s/igm7c97zwp7btc4/rpviewer-2.png?dl=022:29
roaksoaxklj1218: that seems like the bios is trying to boot from a disk that does not have the bootloader on22:37
roaksoaxklj1218: /win 222:37
roaksoaxerr22:37
klj1218roaksoax: yup I agree22:37
klj1218roaksoax: how can I go about debugging to see what device it actually installed centos7 on22:38
roaksoaxklj1218: maas should tell you what device it was installed on, you can see the serial of the device22:40
klj1218roaksoax: where can I see that?22:40
roaksoaxklj1218: in the UI or via the API on the storage section22:41
klj1218roaksoax: ok, yup it installed to an nvme device22:43
klj1218roaksoax: that wasn't the device originally selected in the UI for install ... it was choosing my sda device22:43
klj1218roaksoax: but after the install it has switched it to the nvme0n1-part2... these devices are not bootable from the system BIOS22:44
klj1218roaksoax: so deploying the ubuntu 17.10 image preserves my selection of the sda disk as boot23:03
klj1218roaksoax: but choosing to deploy centos 7 for some reason is switching my boot device to the nvme0n1 device23:06

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