mup | Bug #1736626 opened: [2.4] Cannot add device from dashboard <MAAS:Triaged by ack> <https://launchpad.net/bugs/1736626> | 00:44 |
---|---|---|
mup | Bug #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 | ||
eriklonroth | Hello 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 |
roaksoax | eriklonroth: what type of guide are you looking for ? | 12:36 |
roaksoax | https://pages.ubuntu.com/install-maas.html?utm_source=Twitter&utm_medium=Social&utm_campaign=MAAS_videos& | 12:37 |
mup | Bug #1711370 changed: MAAS installation from Ubuntu Server ISO failing after 08 Aug 2017 <MAAS:New> <https://launchpad.net/bugs/1711370> | 12:41 |
eriklonroth | I'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 | ||
mup | Bug #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 |
klj1218 | looking 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 disk | 19:46 |
klj1218 | https://www.dropbox.com/s/gec92wgjx41c0od/deploy-centos-log.png?dl=0 | 19:47 |
klj1218 | https://www.dropbox.com/s/igm7c97zwp7btc4/rpviewer-2.png?dl=0 | 19:47 |
klj1218 | my systems have 5 disks, 1 ssd and 4 nvme ... if I pull the 4 nvme, the centos install completes and reboots OK | 19:49 |
klj1218 | ubuntu 17.10 install on the same hardware with all disks (5) present works just fine | 19:49 |
klj1218 | trying to find help to debug | 19:50 |
andyshinn | the 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 |
roaksoax | andyshinn: no | 21:50 |
roaksoax | andyshinn: only available via the API | 21:50 |
roaksoax | klj1218: beta2?? you should upgrade to final and re-try | 21:51 |
roaksoax | klj1218: we can't support your if you still running beta2 | 21:51 |
roaksoax | given that final has a lot of fixes | 21:51 |
klj1218 | roaksoax: I installed MASS from 17.10 media, running apt update says "All packages are up to date." | 21:54 |
klj1218 | roaksoax: where should I pull the updates from? | 21:55 |
klj1218 | roaksoax: I'm guessing this will give me the latest 2.3 | 22:03 |
klj1218 | roaksoax: sudo add-apt-repository ppa:maas/stable | 22:03 |
andyshinn | would 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 |
roaksoax | klj1218: yes, the ppa woyuld be good. 2.3 final should be landing in the ubuntu archives soon | 22:21 |
roaksoax | andyshinn: 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 mind | 22:22 |
klj1218 | roaksoax: just updated the system and I'm currently re-running my test | 22:22 |
roaksoax | klj1218: sounds good, let me know how it goes | 22:25 |
roaksoax | klj1218: also, are you sure the BIOS is set to the correct disk for booting, that could be the issue as well | 22:25 |
roaksoax | klj1218: and there's an ongoing discussion over the mailing list | 22:25 |
andyshinn | ok, 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 nice | 22:26 |
klj1218 | roaksoax: oh I will :) | 22:26 |
klj1218 | roaksoax: yup, the BIOS doesn't let me set the NVME disk for boot | 22:26 |
roaksoax | andyshinn: yeah for sure! | 22:26 |
klj1218 | roaksoax: same failure as before | 22:27 |
klj1218 | roaksoax: after the install, which the logs say finished with error, the system reboot from local disk and fails | 22:28 |
klj1218 | roaksoax: this is the screenshot from the console | 22:29 |
klj1218 | https://www.dropbox.com/s/igm7c97zwp7btc4/rpviewer-2.png?dl=0 | 22:29 |
roaksoax | klj1218: that seems like the bios is trying to boot from a disk that does not have the bootloader on | 22:37 |
roaksoax | klj1218: /win 2 | 22:37 |
roaksoax | err | 22:37 |
klj1218 | roaksoax: yup I agree | 22:37 |
klj1218 | roaksoax: how can I go about debugging to see what device it actually installed centos7 on | 22:38 |
roaksoax | klj1218: maas should tell you what device it was installed on, you can see the serial of the device | 22:40 |
klj1218 | roaksoax: where can I see that? | 22:40 |
roaksoax | klj1218: in the UI or via the API on the storage section | 22:41 |
klj1218 | roaksoax: ok, yup it installed to an nvme device | 22:43 |
klj1218 | roaksoax: that wasn't the device originally selected in the UI for install ... it was choosing my sda device | 22:43 |
klj1218 | roaksoax: but after the install it has switched it to the nvme0n1-part2... these devices are not bootable from the system BIOS | 22:44 |
klj1218 | roaksoax: so deploying the ubuntu 17.10 image preserves my selection of the sda disk as boot | 23:03 |
klj1218 | roaksoax: but choosing to deploy centos 7 for some reason is switching my boot device to the nvme0n1 device | 23:06 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!