| roaksoax | terje: cluster controllers/node-groups are deprecated in 2.0. Now we have "rack controllers" | 00:28 |
|---|---|---|
| mup | Bug #1602468 opened: [1.9] loading initial data for maasserver: maas-region-admin reports duplicate key error during package install <cdo-qa> <MAAS:New> <https://launchpad.net/bugs/1602468> | 00:49 |
| mup | Bug #1602477 opened: [2.0b1, UI] MAAS changes the order of DNS servers in the WebUI. <MAAS:Triaged> <MAAS 2.0:Triaged> <MAAS trunk:Triaged> <https://launchpad.net/bugs/1602477> | 01:10 |
| mup | Bug #1602482 opened: [2.0rc2] Incorrect DNS records <MAAS:New> <https://launchpad.net/bugs/1602482> | 01:58 |
| mup | Bug #1602486 opened: [2.0rc1] Rack controller filtering messages out of syslog doesn't work <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1602486> | 02:07 |
| mup | Bug #1602487 opened: [2.0 RC1] Deploying node not powered on - Unable to change power state to 'on' for node krastin: another action is already in progress for that node. <oil> <MAAS:New> <https://launchpad.net/bugs/1602487> | 02:07 |
| mup | Bug #1602486 changed: [2.0rc1] Rack controller filtering messages out of syslog doesn't work <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1602486> | 02:22 |
| mup | Bug #1602487 changed: [2.0 RC1] Deploying node not powered on - Unable to change power state to 'on' for node krastin: another action is already in progress for that node. <oil> <MAAS:New> <https://launchpad.net/bugs/1602487> | 02:22 |
| mup | Bug #1599523 opened: [SRU] MAAS 2.0rc2 to Xenial <maas (Ubuntu):New> <https://launchpad.net/bugs/1599523> | 02:28 |
| mup | Bug #1599523 changed: [SRU] MAAS 2.0rc2 to Xenial <maas (Ubuntu):New> <https://launchpad.net/bugs/1599523> | 02:28 |
| mup | Bug #1602486 opened: [2.0rc1] Rack controller filtering messages out of syslog doesn't work <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1602486> | 02:28 |
| mup | Bug #1602487 opened: [2.0 RC1] Deploying node not powered on - Unable to change power state to 'on' for node krastin: another action is already in progress for that node. <oil> <MAAS:New> <https://launchpad.net/bugs/1602487> | 02:28 |
| mup | Bug #1602488 opened: [2.1rc1] AMT: If I quickly deploy and quickly release a machine, it ends up powered on <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1602488> | 02:28 |
| mup | Bug #1599523 changed: [SRU] MAAS 2.0rc2 to Xenial <maas (Ubuntu):New> <https://launchpad.net/bugs/1599523> | 02:34 |
| mup | Bug #1602488 changed: [2.1rc1] AMT: If I quickly deploy and quickly release a machine, it ends up powered on <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1602488> | 02:34 |
| mup | Bug #1599523 opened: [SRU] MAAS 2.0rc2 to Xenial <maas (Ubuntu):New> <https://launchpad.net/bugs/1599523> | 02:34 |
| mup | Bug #1599523 opened: [SRU] MAAS 2.0rc2 to Xenial <maas (Ubuntu):New> <https://launchpad.net/bugs/1599523> | 02:37 |
| mup | Bug #1599523 changed: [SRU] MAAS 2.0rc2 to Xenial <maas (Ubuntu):New> <https://launchpad.net/bugs/1599523> | 02:37 |
| mup | Bug #1602488 opened: [2.1rc1] AMT: If I quickly deploy and quickly release a machine, it ends up powered on <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1602488> | 02:37 |
| === CyberJacob is now known as zz_CyberJacob | ||
| === zz_CyberJacob is now known as CyberJacob | ||
| mup | Bug #1572340 changed: PXE boot fails when two interfaces are managed <cdo-qa> <cdo-qa-blocker> <pxe> <MAAS:Invalid> <https://launchpad.net/bugs/1572340> | 13:23 |
| mup | Bug #1591250 changed: 1.9.3 changelog information missing from maas.ubuntu.com/docs1.9/changelog.html <cdo-qa> <doc> <MAAS:Fix Released> <https://launchpad.net/bugs/1591250> | 13:23 |
| mup | Bug #1599523 changed: [SRU] MAAS 2.0rc2 to Xenial <verification-needed> <maas (Ubuntu):Fix Released> <maas (Ubuntu Xenial):Fix Committed> <https://launchpad.net/bugs/1599523> | 14:20 |
| mup | Bug #1602721 opened: [2.0rc2] Can't get node-results via cli/api <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1602721> | 14:51 |
| setuid | Anyone here using sstreams-mirror? | 14:52 |
| setuid | I'm trying to figure out how to get simplestreams to sync -both- amd64 and i386 in the same command. If I run them in two separate commands, passing each arch, the second pass wipes out the mirror ffrom the first pass | 14:53 |
| roaksoax | setuid: in the filter you'd do something like amd64|i386 or similar | 14:55 |
| roaksoax | can't remember of the top of my head | 14:55 |
| roaksoax | smoser: ^^ do you ? | 14:55 |
| smoser | setuid, 'arch~(i386|amd64)' | 14:56 |
| setuid | I've tried all of the obvious array expansions, without luck | 14:56 |
| smoser | you have to do regex. | 14:56 |
| setuid | hrm, ok... I'll give that one a shot. Tried , : space, and others... pipe it is! | 14:56 |
| smoser | its regex | 14:56 |
| smoser | i didn't write that. talk to larry wall i think | 14:56 |
| smoser | it was the simplist immediately powerful well defined operator | 14:57 |
| setuid | right, wasn't easy to find the parsing bit of simplestreams.py for what pcre they were using | 14:57 |
| setuid | one moment, giving that a shot now | 14:57 |
| setuid | Looks like its working... now if I could only do release and daily in the same pass but I'll add a second line for that | 14:59 |
| setuid | it's not picking up xenial, only precise and trusty, even though I see xenial in the repo I'm pointing to | 14:59 |
| setuid | https://images.maas.io/ephemeral-v2/daily/ | 15:00 |
| mup | Bug #1602721 changed: [2.0rc2] Can't get node-results via cli/api <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1602721> | 15:00 |
| setuid | passing in: 'release~(xenial|trusty|precise)' | 15:00 |
| mup | Bug #1602721 opened: [2.0rc2] Can't get node-results via cli/api <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1602721> | 15:03 |
| mup | Bug #1602721 changed: [2.0rc2] Can't get node-results via cli/api <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1602721> | 15:06 |
| mup | Bug #1602721 opened: [2.0rc2] Can't get node-results via cli/api <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1602721> | 15:15 |
| terje | thansk roaksoax | 15:18 |
| terje | I have an idea that I'm trying to persue. Just wish to vet it here. | 15:18 |
| terje | I'm installing xenial on baremetal and installing maas there. Then, using uvtool, I'm creating an xenial VM, where I'd like to install juju-core. | 15:19 |
| terje | and bootstrap that instance of juju to my instance of maas. | 15:20 |
| terje | does this idea make sense or is there perhaps a better way to do that? | 15:20 |
| setuid | terje, functionally, they're different machines to juju, so it shouldn't ma... wait, you're going to use juju inside a maas-managed kvm instance, to update maas? | 15:44 |
| setuid | Why not use the baremetal and install maas in a kvm instance, then use a second kvm instance to run juju | 15:45 |
| setuid | that way, you can swap out your main maas kvm instance with another as needed for rolling upgrades/downgrades/updates/testing | 15:45 |
| setuid | If maas is installed on your baremetal box, you're locked in | 15:46 |
| setuid | Unless I misunderstood your goal | 15:46 |
| mup | Bug #1594991 opened: [2.0RC1] MAAS displays every power query on the summarized view of node event log <oil> <MAAS:Triaged> <MAAS 2.0:New> <MAAS trunk:Triaged> <https://launchpad.net/bugs/1594991> | 16:39 |
| setuid | smoser, Weird, I am trying to sync the daily images, but it's only getting trusty and precise, despite adding yakkety and xenial to the sstream command... and I can see them in the directory, so they ARE there | 17:12 |
| setuid | https://images.maas.io/ephemeral-v2/daily/xenial/ | 17:12 |
| setuid | command I'm using is: | 17:12 |
| setuid | sudo /usr/bin/sstream-mirror --keyring=/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg https://images.maas.io/ephemeral-v2/daily/ /maas/images/ephemeral-v2/daily/ 'arch~(amd64)' 'subarch~(generic|hwe-t)' 'release~(yakkety|xenial)' --max=1 --verbose | 17:12 |
| === mup_ is now known as mup | ||
| smoser | setuid, if you add a -v i think it will tell you that it filtered them out | 17:31 |
| smoser | but its filtering out becauase subarch is the "primary subarch" | 17:31 |
| smoser | subarches (plural) is a comma delimited list of subarches that are supported. | 17:31 |
| smoser | so actually, the easiest thing for you to do is to *drop* the subarch~ entirely | 17:32 |
| smoser | and it will dtrt | 17:32 |
| setuid | ah! | 17:32 |
| setuid | for both daily and releases, I bet... trying that now | 17:32 |
| setuid | Goes from 2.8Gb to 17Gb | 17:33 |
| terje | setuid: ok, that's a good idea. | 18:13 |
| terje | baremetal, +2 uvt-kvm instances (maas, juju) | 18:14 |
| terje | only, uvt-kvm wants to use the 'default' network in libvirt (192.168.122/24). | 18:15 |
| terje | so my maas server won't see the pxe requestws | 18:16 |
| terje | so, prolly that's not going to work. :/ | 18:16 |
| mup | Bug #1556137 changed: Juju 2.0: cannot connect to LXC container when deploying bundle with LXC container placement with maas 1.9.1 as provider <2.0-count> <oil> <juju-core:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1556137> | 19:30 |
| mup | Bug #1556137 opened: Juju 2.0: cannot connect to LXC container when deploying bundle with LXC container placement with maas 1.9.1 as provider <2.0-count> <oil> <juju-core:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1556137> | 19:51 |
| mup | Bug #1556137 changed: Juju 2.0: cannot connect to LXC container when deploying bundle with LXC container placement with maas 1.9.1 as provider <2.0-count> <oil> <juju-core:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1556137> | 19:54 |
| terje | Hi smoser, I see you worked on this issue: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1563296 | 21:06 |
| terje | Is the fix still to add /etc/cloud/cloud.cfg.d/99-snappy-disable-network-config.cfg ? | 21:06 |
| terje | even in xenial? | 21:06 |
| mup | Bug #1602846 opened: 502 proxy errors after upgrading to MAAS 2.0 rc2 <oil> <MAAS:New> <https://launchpad.net/bugs/1602846> | 21:28 |
| mup | Bug #1602848 opened: Spurious failure in test_get_hostname_ip_mapping_returns_fqdn_and_other <tests> <MAAS:Triaged> <https://launchpad.net/bugs/1602848> | 21:28 |
| mup | Bug #1602850 opened: Update Maas 2.0 Documentation to include the "maas-rack support-dump" feature <MAAS:New> <https://launchpad.net/bugs/1602850> | 21:28 |
| mattrae | hi, where is the django controller for the api call that returns nodes interfaces to cloud-init for curtin? | 22:35 |
| mup | Bug #1598358 opened: Node is started but not deployed <oil> <oil-2.0> <juju-core:New> <MAAS:New> <https://launchpad.net/bugs/1598358> | 23:37 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!