[04:34] Bug #1576987 changed: package tgt 1:1.0.63-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[07:28] hi does anyone have any insight into this issue ? [07:28] https://bugs.launchpad.net/maas/+bug/1658718 [08:22] Hello. Do I need to keep NetBoot on nodes when using MAAS? [08:24] filiplt, aka PXE, yes [08:26] @brendand do you have any insight on the centos 7 hanging install issue? [08:27] bryanb229, not much beyond what's in the bug. i think it's efi related so you could get around it by switching to legacy bios, i think [08:27] cool thanks will give it a try [08:28] thank you, brendand [09:04] Hello I want to import a raw image to deploy it with MaaS but I dont know how to do so [09:04] can anyone here help me with this [09:10] sarah_, you need to use the cli 'boot-resources create' [09:11] here's the command I did and here's the error [09:12] sudo maas admin boot-resources create name=custom/proxmox title="proxmox" architecture=custom/amd64 content@=/home/myra/proxmox.raw [09:12] {"architecture": ["'custom/amd64' is not a valid architecture. It should be one of: ''."]} [09:13] sarah_, can you try instead 'amd64/generic' [09:18] it takes a while to respond [09:18] {"architecture": ["'amd64/generic' is not a valid architecture. It should be one of: ''."]} [09:26] sarah_, do you have any other images synced? [09:27] yes, I do have a 16.04 LTS amd64 ubuntu [09:28] sarah_, which version? [09:28] of maas ? 2.1 [09:50] hello ? [09:53] sarah_, i'm not 100% sure at the moment, need to think [09:55] Ive been stuck for over three days now [09:55] Bug #1676330 opened: [CLI] Missing functionality to lookup system ID from machines power-parameters query [09:57] sarah_, can i get the exact maas version? it should be down at the bottom of the ui [09:57] or you can run dpkg on the maas server [09:57] MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1) [10:00] sarah_, now boot-resources read [10:01] http://paste.ubuntu.com/24259922/ [10:05] sarah_, log in to the maas server, run 'maas-region shell' and then these commands : http://paste.ubuntu.com/24259927/ [10:08] this is the output http://paste.ubuntu.com/24260031/ [10:12] sarah_, next i'd try rack-controllers read [10:13] doesnt that need a specific node ? [10:14] sarah_, no, that lists all rack-controllers [10:15] http://paste.ubuntu.com/24260100/ [10:16] sarah_, then rack-controller list-boot-images c6a6hx [10:17] http://paste.ubuntu.com/24260115/ [10:18] all looks good. i'm mystified [10:18] * brendand thinks more [10:19] so why doesnt it work ? [10:28] sarah_, more code for the maas-region shell: [10:28] >>> from maasserver.models import BootResource [10:28] >>> BootResource.objects.get_usable_architectures() [10:31] the output : ['amd64/generic'] [10:31] can you try again then? with the same command? [10:32] to create the boot resource [10:43] it's taking forever to respond now [10:43] sarah_, that's good [10:44] sarah_, it won't finish until the image is uploaded [10:44] shouldnt it output something ? [10:45] sarah_, no - it's a restful api, there's no allowance for progress reporting [10:45] oh okay [10:46] you could argue there should be an asynchronous version, but there isn't [10:49] Any hint how to troubleshoot node deployment, when it finishes with "cloud-init[1859]: Can not apply stage final, no datasource found! Likely bad things to come!"? I've put node in rescue mode, checked network conectivity with MAAS controller. [10:54] sarah_, btw you might want to actually upload it as ddtgz [10:54] I thought it supposed to be a raw image [10:54] sarah_, default is tgz which is a tarball of the rootfs, but if it's a dd of the rootfs that's been tarred then it's that [10:55] sarah_, where is that mentioned? [10:56] I dont remember Ive been through so many forums and stuff [10:56] I made the image with openstack, I converted it from qcow2 to raw [10:57] but it still didnt output anything, does that mean it's working ? [10:57] sarah_, it should. it might take a really long time depending on the connection speed and the size of the content [11:02] oh okay I hope it works and if it doesnt Ill upload it as a ddtgz [11:03] thank you so much [11:04] sarah_, btw the reason for the initial error was probably just that it didn't get time to sync up [11:11] It finished but there was no output [11:11] does that mean it worked? [11:11] sarah_, that's normal [11:11] sarah_, check it's listed in boot-resources read [11:16] Bug #1676391 opened: [CLI] Missing functionality to lookup interface ID by device name [12:08] I dont think it worked because its nowhere to be found in the images webpage [12:09] @brendand [12:13] sarah_, what about in boot-resources read? [12:16] it is there [12:16] but how do I use in the in web interface [12:17] sarah_, you 'use' it by deploying it to a machine [12:17] sarah_, it should appear as an option when deploying [12:18] There will be a 'Choose your image:' dialog [12:20] oh okay thank you so much [14:12] Hey, what is the "maas $PROFILE machine restore-network-configuration $SYSTEM_ID" command supposed to do exactly? On 2.1.4, the only thing it's doing is adding an alias to the default interface used by MAAS. === stormmore is now known as Budgie^Smore [15:08] Bug #1676461 opened: Interface links differ from newly commissioned nodes vs recommissioned nodes with previously set interfaces === narinder is now known as narinder_out === aimeeu__ is now known as aimeeu === narinder_out is now known as narinder [20:35] Bug #1575815 changed: [1.9] NIC previously discovered through commissioning no longer connected to Maas network [20:35] Bug #1628535 changed: AH00493: SIGUSR1 received. Doing graceful restart - Apache2 crashes - Can't access maas server URL [20:35] Bug #1631421 changed: [2.1b2] failure to deploy all systems that lasted until reboot of maas container [21:14] Bug #1676619 opened: dnsresources create fails on valid IP [22:17] Bug #1675887 changed: [2.1] Commissioning fails to detect drives. [22:26] Bug #1675887 opened: [2.1] Commissioning fails to detect drives. [22:35] Bug #1675887 changed: [2.1] Commissioning fails to detect drives. [22:55] Hola [23:35] Bug #1674658 changed: [2.1] setting larger MTU on vlan does not set MTU on base device [23:47] Bug #1674658 opened: [2.1] setting larger MTU on vlan does not set MTU on base device [23:50] Bug #1674658 changed: [2.1] setting larger MTU on vlan does not set MTU on base device