[01:37] <anastasiamac> wallyworld: if/when u have time PTAL - https://github.com/juju/juju/pull/8989
[01:37] <anastasiamac> wallyworld: azure bits for cc invalidation
[01:37] <wallyworld> ok
[03:43] <veebers> wallyworld: when you have a moment can we chat real quick
[04:03] <wallyworld> veebers: did you want a hangout?
[04:03] <veebers> wallyworld: yes please, standup?
[04:04] <wallyworld> sure
[10:16] <rick_h_> zeestrat: ping, I wanted to make sure you saw my reply on the constraints and wanted to ask permission to delete the posts in there not about the spec in discussion. If we wanted to we can recreate the posts on the 2.4.1 release notes post instead?
[11:49] <Amar_> HELP
[11:49] <Amar_> LXD containers are remaining in pending state for ever in juju 2.4 for trusty series
[11:50] <rick_h_> Amar_: need a  bit more background. So LXD was pre-trusty if the host is trusty I don't think that's going to work out. Are you on xenial or later and trying to create a trusty container?
[11:51] <rick_h_> Amar_: you'll have to look into the juju status --format=yaml and see if there's any machine details there
[11:51] <rick_h_> Amar_: or look at the logs on the host, including lxd logs
[11:51] <Amar_> the host is trusty
[11:52] <rick_h_> Amar_: so the only reason we've kept Juju 1.25 around is that upgrading from trusty->xenial meant going from lxc to lxd and so I don't think that's going to work out well.
[11:52] <zeestrat> rick_h_: ahoy. Yeah, it's OT so please move as you see fit. My bad regarding the mention in the 2.4.1 release notes. I read that as only for the LXD provider/cloud and not the "deploy service in constrained LXD container on different clouds such as MAAS". A little example and heads up in the bug would help next time :)
[11:53] <rick_h_> zeestrat: no doubt, and filed a card to get that docs urls updated
[11:53] <rick_h_> zeestrat: I thought we did have updated docs so will chat with docs folks to see if a release button didn't get pushed or what
[11:53] <Amar_> Agree.. but I had two different setup one is JUJU 2.3 and another is juju 2.4.
[11:54] <Amar_> In juju 2.3 I am able to create a trusty LXD container on a trusty host, but on 2.4 I am not able to do so
[11:55] <Amar_> Last login: Mon Jul 30 04:02:13 2018 from 192.168.224.2 root@juju:~# juju --version 2.4.0-xenial-amd64 root@juju:~# juju status --format=yaml model:   name: default   type: iaas   controller: cplane-controller   cloud: cplane   version: 2.4.0   model-status:     current: available     since: 30 Jul 2018 04:06:27-07:00   sla: unsupported machines:   "0":     juju-status:       current: started       since: 30 Jul 2018 04:20:08-07:00     
[11:55] <zeestrat> rick_h_: Roger. Thanks for following up.
[11:56] <rick_h_> Amar_: can you file a bug please with details of the setup?
[11:56] <Amar_> The error I am getting is "machine-0: 04:55:56 ERROR juju.provisioner starting container provisioner for lxd: initialising container infrastructure on host machine: creating LXD container manager: Get http://unix.socket/1.0: dial unix /var/lib/lxd/unix.socket: connect: no such file or directory machine-0: 04:56:08 WARNING juju.provisioner not stopping machine agent container watcher due to error: initialising container infrastructure on
[11:56] <rick_h_> Amar_: e.g. controller/model versions and what the deployment on the containers looks like (e.g. juju status output
[11:56] <Amar_> Sure.
[11:57] <rick_h_> Amar_: that looks like no lxd running/listening
[11:57] <Amar_> Yes.. No LXD service is installed in the host.
[11:58] <Amar_> is there I had to look into cloud init..
[11:58] <rick_h_> Amar_: any hint in cloud init logs what went wrong?
[12:00] <Amar_> Other setup: root@juju-server:~# juju --version 2.3.5-xenial-amd64
[12:00] <Amar_> 15        started  10.10.11.82   qkxxhs                trusty  default  Deployed 15/lxd/2  started  10.10.11.83   juju-738146-15-lxd-2  trusty  default  Container started
[12:01] <Amar_> Logs let me get the cloud init logs
[12:03] <Amar_> Rick_h: No errors in cloud_init logs
[12:04] <rick_h_> Amar_: k, so is lxd on that system but not running? e.g. did the service die?
[12:05] <Amar_> Rick_h: No lxd service installed on the host
[12:07] <Amar_> No lxd service found.. even its had not created the lxdbr0 bridge
[12:09] <rick_h_> Amar_: you've puzzled me. I thought lxd wasn't supported in trusty but you're showing me you've got it working. I'll have to get some digging. Please go the bug route and we'll have to get some folks to chase paths in code to see what's up.
[12:09] <rick_h_> s/puzzled/stumped
[12:09] <Amar_> ok.. will file a bug
[12:10] <rick_h_> Amar_: ty
[12:25] <Amar_> Thanks Rick_h
[13:28] <pmatulis> manadart, i updated the bug. i don't see a limits.memory line
[13:35] <manadart> pmatulis: Ack. Needs checking out then.
[20:51] <veebers> Morning all o/
[20:52] <thumper> morning
[20:52] <thumper> veebers: do you know what the situation is with the google cloud ci account?
[20:54] <veebers> thumper: in what sense? Have you seen Pats reply?
[20:54] <thumper> no, just seeing a lot of emails
[20:55] <thumper> I'll look for Pat's reply
[20:55] <veebers> thumper: essentially it's probably a credit card thing
[21:40] <hml> wallyworld: if you have a few minutes today, your eyes on: https://github.com/juju/juju/pull/8984 would be appreciated.  :-)
[21:40] <wallyworld> hml: willdo, sorry, i missed the email :-( rick has already told me i'm bad
[21:41] <hml> wallyworld: no worries, i figured it got lost in the github emails.  should have sent a direct email.  :-)  ty
[21:42] <wallyworld> no worries. yeah, i get flooded with gh emails
[22:02] <thumper> babbageclunk: I'm going to have to push off our 1:1 so I can go and collect a sick child
[22:02] <thumper> babbageclunk: chat after lunch?
[22:03] <babbageclunk> thumper: ok - hope the child's alright
[22:04] <thumper> she is just feeling nauseous