[03:52] Bug #1526859 opened: Only latest LTS is shown in the Settings page [03:55] Bug #1526859 changed: Only latest LTS is shown in the Settings page [03:58] Bug #1526859 opened: Only latest LTS is shown in the Settings page [04:01] Bug #1526859 changed: Only latest LTS is shown in the Settings page [04:04] Bug #1526859 opened: Only latest LTS is shown in the Settings page === sebastien is now known as Guest90872 [15:08] Bug #1527634 opened: [1.10] Disk erasing with Xenial results it abnormal poweroff [15:48] hi, a typical setup of MaaS only has a single region controller running? [16:21] tiagogomes: that's correct, we don't yet support multiple regions [16:23] roaksoax thanks. I am very new to this, so probably this is a daft question, but can you use MaaS to deploy JuJu, so that JuJu orchestrates software in VMs running instead of the baremetal itself [16:24] s/ in VMs running/running in VMs/ [16:59] Bug #1527684 opened: Use python-ilo vs. IPMI for HP Boxes [17:10] tiagogomes: you use juju alongside maas to do that. MAAS is just the "hardware" provider [17:11] tiagogomes: juju has different providers, ec2, openstck, ..., maas. [17:11] Bug #1527684 changed: Use python-ilo vs. IPMI for HP Boxes [17:14] Bug #1527684 opened: Use python-ilo vs. IPMI for HP Boxes [17:14] Bug #1527688 opened: maas web ui gives error: Unable to connect to: ws://10.230.56.2/MAAS/ws [17:27] I would like to bootstrap JuJu on top of MaaS, so that the JuJu state machine would run in the baremetal. But once JuJu was boostrapped, I would like to deploy applications with JuJu in virtual machines [17:44] Bug #1527688 changed: maas web ui gives error: Unable to connect to: ws://10.230.56.2/MAAS/ws [17:53] Bug #1527699 opened: MAAS documentation still uses port 80 even though it's deprecated [17:56] Bug #1527699 changed: MAAS documentation still uses port 80 even though it's deprecated [18:11] Bug #1527699 opened: MAAS documentation still uses port 80 even though it's deprecated [20:37] hey guys, I'm trying to get some custom curtin stuff running when juju deploys, but it seems like it's not running any of the stuff in the preseed file, any advice on what to look at? [20:37] followed this --> https://www.stackevolution.com/node/17 [20:38] and --> https://www.stackevolution.com/node/20 [20:38] both of which I want [21:19] from `maas root boot-resources import`: "gpg --batch --verify --keyring=... Signature made Wed Nov 4 16:09:43 2015 EST ... BAD signature from \"Ubuntu Cloud Image Builder...\"" [21:20] this is the single google result for "bad signature from ubuntu cloud image builder" [21:20] http://irclogs.ubuntu.com/2015/09/01/%23ubuntu-server.html [21:20] to get here, i followed these instructions: https://maas.ubuntu.com/docs/sstreams-mirror.html [21:21] but swapped out "daily" for "releases" [21:21] then tar'd up the resulting mirror and moved it to my maas server [21:21] and now the images won't import with that error [21:23] it sure looks like the current trusty releases streams metadata files (https://maas.ubuntu.com/images/ephemeral-v2/releases/streams/v1/) have had bad signatures for more than a month [21:23] i bet i'm doing something wrong, but... [21:23] I did the mirror thing, but I didn't try reimporting the images [21:24] wonder if I will have the same issue [21:24] i'd be interested to find out [21:24] spaok: from releases or from daily? [21:25] that might be my mistake, but i'm not sure why "releases" and "daily" would mean something different than what one would expect them to mean [21:25] rlease [21:25] release [21:25] k [21:25] i do [21:25] sstream-mirror --keyring=/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg http://maas.ubuntu.com/images/ephemeral-v2/releases/ /var/www/html/images/ephemeral-v2/releases 'arch=amd64' 'release~(trusty|wily)' --max=1 [21:26] you left out the subarch thing? [21:26] ya, cause it wasn't working for wily [21:26] also, i have some systems that are still on 12.04, so i used trusty|precise as documented [21:27] (that should go away, but i didn't want to have to make the mirror again [21:27] ) [21:28] i'm still just trying to get my head around how to use ubuntu and MAAS, for some reason my preseeding stuff isn't working [21:28] what i'm not sure about is: [21:28] the contents of https://maas.ubuntu.com/images/ephemeral-v2/releases/streams/v1/index.json.gpg and the PGP block at the bottom of the index.sjson file are different [21:28] and i'm not sure if that's the way it's supposed to be [21:28] spaok: i dunno, i haven't gotten to preseed yet [21:30] caturday: ya I'm not sure about the keys, I'm kinda just stumbling around with those, I have mirror scripts for most stuff and a lot of them I imported the gpg keys to a local mirror key file, but streams if diffferent than debmirroring it seems [21:30] I [21:30] I'm justing wondering if these images are curtin or debianinstaller ones [21:31] i was able to get this to work on a different machine using daily, and those were curtin [21:31] cause neither of the preseeds seem to work for me [21:31] kk, maybe I'll try those [21:31] k === wojdev_ is now known as wojdev [21:32] I'm way to used to rhel [21:50] caturday: I believe inline PGP signatures are different from detached PGP signatures. [21:50] caturday: I looked into trying to use a single signature for both, and it's awkward at best. [21:51] caturday: they should both validate though. [21:51] caturday: .sjson exists to avoid mirror update race conditions. [22:05] rbasak: i'll have to looked into testing them on monday...i've left work :D [22:05] rbasak: but thanks for the pointer [22:27] caturday: negitive on updated images running preseeds for me [22:27] not really sure what is going on