| === frankban|afk is now known as frankban | ||
| === chrome0_ is now known as chrome0 | ||
| magicaltrout | is it me | 11:18 |
|---|---|---|
| magicaltrout | or is the jujucharm store borked? | 11:18 |
| magicaltrout | oh no | 11:19 |
| magicaltrout | its me :) | 11:19 |
| bdx | gsamfira: I think my bug is your bug too | 17:24 |
| bdx | aha | 17:24 |
| bdx | I didn't realize it yesterday | 17:24 |
| gsamfira | bdx: looks like it :D | 17:28 |
| bdx | gsamfira: does the fix in proposed work for you? | 17:34 |
| bdx | testing it now | 17:34 |
| gsamfira | bdx: we went with 2.2.6 for now. If it helps you out, I can test it as well, but for the moment we're good to go | 17:38 |
| ybaumy | i just wanted to say great job on the current vsphere support | 17:39 |
| bdx | gsamfira: I just added the proposed repo, deploying a few nodes now | 17:40 |
| ybaumy | if anyone wants to hear that .. kubernetes and juju has now a chance again in our company | 17:40 |
| bdx | ybaumy: 2.3.1 got some vsphere love eh? | 17:41 |
| ybaumy | bdx i love it so far. we are currently using openshift from redhat but i want to push ubuntu and juju | 17:41 |
| bdx | ybaumy: awesome. srry I'm a bit behind on the vsphere provider .... what changed? | 17:42 |
| ybaumy | bdx last time it was not working at all for me :D so that changed .. i was using maas as cloud provider with vsphere and then juju to deploy kubernetes... i dont need maas anymore | 17:44 |
| bdx | ybaumy: sweet! | 17:47 |
| ybaumy | bdx its so easy to scale and roll out a cluster | 17:52 |
| ybaumy | bdx: you should try it | 17:53 |
| bdx | ybaumy: I can't think of any reason to use the vmware provider | 17:54 |
| bdx | but if I ever do have a use case for it | 17:55 |
| bdx | I'll ping you and get the dl | 17:55 |
| bdx | glad to hear its purring along for you though | 17:55 |
| bdx | ybaumy: on second thought I may have some deploys that will require esxi in the next year | 17:56 |
| bdx | totally spaced it | 17:56 |
| bdx | so yeah, really good to know | 17:56 |
| bdx | gsamfira: http://paste.ubuntu.com/26178059/ | 18:05 |
| bdx | :) :) :) :) | 18:05 |
| gsamfira | bdx: outstanding! that was a quick fix :D | 18:21 |
| gsamfira | hopefully there was a CI test added for this case :P | 18:21 |
| rick_h | gsamfira: looks like it was something that changed in the fan package used. definitely some room to make sure that the new versions of the fan are tested out | 18:32 |
| gnuoy | has JUJU_REMOTE_UNIT gone ? | 18:37 |
| gnuoy | http://paste.ubuntu.com/26178222/ <- I'm seeing this in a debug hooks session | 18:38 |
| gnuoy | JUJU_VERSION=2.3.1 | 18:38 |
| * gnuoy looks for release notes | 18:38 | |
| gnuoy | argh thedac just put me right, I'm not in a relation hook | 18:41 |
| McL0v1n_ | Greetings! When i deploy to a host and lxc (im deploying the openstack bundle) my containers dont start up. Ive waited for hours thinking it was the image download but the only way i can get them to start up is if i log into each host and run lxd init. Shouldnt juju be starting them up on its own? | 19:22 |
| McL0v1n_ | Anyone around? | 19:56 |
| thedac | I am seeing something similar: http://pastebin.ubuntu.com/26178643/ | 19:59 |
| thedac | McL0v1n_: what version are you running? | 19:59 |
| thedac | I have 2.4-beta1-artful-amd64 snap installed but the controller is on 2.3-rc2. I am going to try with a new controller | 20:00 |
| McL0v1n_ | Im using the stable from the repo, not the snap | 20:05 |
| McL0v1n_ | Im at a clients office 2 hours away from my cabinet, so i cant look at it and im using IRC on my phone | 20:06 |
| thedac | McL0v1n_: no worries, I'll try this new controller and file a bug | 20:07 |
| McL0v1n_ | Essentially maas from apt repo, juju from apt repo, ubuntu 16.04 image from maas | 20:07 |
| McL0v1n_ | Thanks, this have been bothering me for months now and i cant find anything that relates to it | 20:07 |
| hml | i’m able run a container with openstack using 2.3.2 | 20:09 |
| McL0v1n_ | Im not doing anything different from a standard deploy: a bunch of bare metal servers and maas | 20:10 |
| McL0v1n_ | Using openstack-base bundle #50 and now #51 | 20:11 |
| McL0v1n_ | I can check the actual versions when i get back to my office | 20:13 |
| McL0v1n_ | This has been happening from back when i tried to do it all based of the exact instructions for autopilot. Exact same issue. So it has to be a juju thing | 20:16 |
| zeestrat | McL0v1n_: you mentioned bridge activation issues? Something like this? https://bugs.launchpad.net/maas/+bug/1736022 | 20:17 |
| mup | Bug #1736022: failed to bridge devices: bridge activaction error: bridge activation failed: Killed old client process <juju> <juju:Incomplete> <MAAS:Incomplete> <https://launchpad.net/bugs/1736022> | 20:17 |
| McL0v1n_ | Different issue, but i ONLY get that when i manually log into each host and run lxd init | 20:18 |
| McL0v1n_ | If i dont the container never starts up | 20:18 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!