[00:04] <redir> perrito666: yt?
[00:04] <perrito666> redir: always
[00:04] <redir> great
[00:05] <redir> so looking at bug 1577776
[00:05] <mup> Bug #1577776: 2.0b6: asks for domain-name, then doesn't know what it is <juju-release-support> <landscape> <rc1> <usability> <juju-core:Triaged> <https://launchpad.net/bugs/1577776>
[00:05] <alexisb_> sorry menn0 wallyworld and I are running over
[00:05]  * perrito666 clicks
[00:05] <perrito666> redir: ok
[00:06] <redir> You added 'domain-name' to the credential config for opentack
[00:06] <redir> yes?
[00:08] <redir> I can add it to the openstack environ schema and provider configurator... but is there more that needs to happen?
[00:08] <perrito666> redir: I believe so, for keystone 3
[00:09] <redir> Apparently I am getting kicked from the conf room.
[00:09] <perrito666> redir: not sure really, the underlying code should be there (I am a bit worried that this bug exists)
[00:09] <redir> OK. I'll find you later tonight or more likely tomorrow
[00:10] <redir> perrito666: me too since it seems that something got nuked or was never tested
[00:10] <redir> bbiab
[00:10] <redir> or tomorrow
[00:10] <perrito666> redir: k
[00:16] <alexisb_> menn0, are you still available to meet or did you want to skip this week?
[00:17] <menn0> alexisb_: I'm available now. I waited around for a while for you.
[00:17] <menn0> alexisb_: I don't have anything major to discuss except maybe the sprint review workshops.
[00:23] <alexisb_> menn0, I can join for a bit
[00:23] <alexisb_> I will hop on
[00:23] <perrito666> k, eod, CUALL tomorrow
[00:42] <thumper> bugger
[00:42] <thumper> CreateMutex with a name doesn't give us the semantics we want on windows for the mutex
[00:42]  * thumper digs some more into windows world
[00:48] <thumper> hmm...
[00:48] <thumper> dog walk time, then I'll try something else
[01:06] <axw> wallyworld: http://reviews.vapour.ws/r/5072/ -- I'll test with manual now
[01:07] <wallyworld> ta, looking
[01:14] <wallyworld> axw: lgtm. works on lxd i assume as well
[01:15] <axw> wallyworld: will lxd test shortly, pretty certain it will
[01:16] <wallyworld> yeah, looks like it will
[01:36] <axw> wallyworld: seems there's a different issue with manual, investigating/fixing in a follow up
[01:36] <wallyworld> ok
[01:36] <axw> wallyworld: I'm getting "creating hosted model: model already exists" -- possibly the same thing the grnet folks are getting
[01:37] <wallyworld> axw: was that grnet issue preceeding this work then?
[01:37] <axw> wallyworld: the issue the found was before you landed my changes, if that's what you mean
[01:37] <wallyworld> yeah
[01:38] <wallyworld> so good to fix
[01:38] <axw> well I don't know if it's what they're seeing, but need to fix it anyway
[01:38] <axw> we'll see
[01:41] <wallyworld> axw: is there a bug number?
[01:42] <axw> wallyworld: no, it was on the mailing list. about the synnefo provider
[01:42] <axw> I'll create a bug for the issue I'm seeing now tho
[01:42] <wallyworld> ok, ta
[01:43] <axw> wallyworld: actually I suspect it's different, I think it's to do with detecting regions
[01:43] <wallyworld> rightio. we should maybe test all providers we can to be sure
[01:43] <axw> cloud says it has no regions, but if you bootstrap manual/<IP> then that goes in as a region
[01:44] <axw> altho hm I think we add that in.. anyway, I'll look into it and stop guessing
[02:06] <mup> Bug #1593033 opened: manual: bootstrapping fails with "creating hosted model: model already exists" <blocker> <juju-core:In Progress> <https://launchpad.net/bugs/1593033>
[02:33] <menn0> thumper: simple bit of infrastructure I need for current MM work: http://reviews.vapour.ws/r/5074/
[02:45] <axw> wallyworld: http://reviews.vapour.ws/r/5075/
[02:45] <wallyworld> looking
[02:53] <wallyworld> axw: lgtm to but it seems there's a bit of test coverage missing unless i missed it
[02:57] <axw> wallyworld: yeah, because it's a PITA to inject/test with custom environ providers. I'll see if I can make an incremental improvement...
[02:58] <wallyworld> axw: we can land for the beta and do in a follow up, let's get the merge happening, so long as you've tested by hand
[02:59] <wallyworld> axw: also, could you add a few lines to the release notes about this and the cloud/cred/addmodel changes, eg for add model a user visible change is that the --credential argument doesn't take a cloud name prefix anymore
[03:02] <axw> wallyworld: yep. I'll mention --region, but it's not fully baked yet because you still have to specify region in --config
[03:02] <axw> wallyworld: on account of us still storing cloud/cred details in model config
[03:03] <wallyworld> no worries, just the minimal so folks know what to do and are given info on what's different. i have to do a bit on shared config also
[03:03] <wallyworld> axw: also, when you're free, i have pushed that controller uuid change, but i'll land after the beta revision is finalised
[03:04] <axw> wallyworld: ok. still gotta look into the CreateModel compatibility
[03:04] <wallyworld> yep, that takes priority for sure
[03:12] <axw> wallyworld: bleh, GUI uses ConfigSkeleton
[03:12] <wallyworld> fark
[03:12] <wallyworld> we'll have to put it back for now and let them know to remove it
[03:12] <axw> I guess I'll put it back in, in some minimal form
[03:26] <thumper> fuck yeah!!
[03:26] <thumper> got windows working too
[03:26] <thumper> can't use a mutex because of stupid windows thread bollocks
[03:27] <thumper> if the current thread already owns the mutex, any call to wait for that mutex succeeds
[03:27] <thumper> so I'm using a named semaphore
[03:27] <thumper> with a max count of 1
[03:27] <thumper> that works
[03:27] <thumper> phew
[03:28] <davecheney> wow, that could have been a buzzkill
[03:33] <mup> Bug #1593042 opened: Juju GUI cannot create new models <blocker> <juju-core:In Progress by axwalk> <https://launchpad.net/bugs/1593042>
[03:39] <thumper> davecheney: but windows mutex now has exactly the same behaviour as iOS and linux
[03:40] <thumper> I'm busy adding docstrings
[03:40] <thumper> and a few extra tests
[03:40] <davecheney> sgtm
[03:45] <axw> wallyworld: http://reviews.vapour.ws/r/5076/
[03:45] <wallyworld> looking
[03:49] <wallyworld> axw: was hoping it would be simple like that. i did something similar for deploy with adding vs not adding charms
[03:55] <axw> wallyworld: the existing release notes don't say anything about a cloud prefix on --credential
[03:55] <wallyworld> well, looks like that omission is now fixed :-)
[03:56] <axw> wallyworld: on second thoughts, I think we should just be silent about --region until it's fully supported
[03:56] <wallyworld> ok
[04:15] <menn0> thumper: migration minion now reporting to master: http://reviews.vapour.ws/r/5077/
[04:15] <thumper> meetingology: ool
[04:15] <meetingology> thumper: Error: "ool" is not a valid command.
[04:15] <thumper> oops
[04:16] <thumper> ugh
[04:16] <thumper> meetingology: cool
[04:16] <meetingology> thumper: Error: "cool" is not a valid command.
[04:16] <thumper> menn0: cool
[04:16] <thumper> who asked meetingology along anyway
[04:16] <menn0> thumper: it should have been broken up into smaller PRs, but it's not actually that big overall
[04:16] <menn0> thumper: what is meetingology ?
[04:16] <thumper> a bot by the look of it
[04:16] <menn0> I got that :)
[04:17] <menn0> meetingology: help
[04:17] <meetingology> menn0: (help [<plugin>] [<command>]) -- This command gives a useful description of what <command> does. <plugin> is only necessary if the command is in more than one plugin. You may also want to use the 'list' command to list all available plugins and commands.
[04:17] <menn0> meetingology: list
[04:17] <meetingology> menn0: Admin, Channel, Config, MeetBot, Misc, NickAuth, NickCapture, Owner, and User
[04:17] <menn0> meetingology: Owner
[04:17] <meetingology> menn0: Error: "Owner" is not a valid command.
[04:17] <menn0> meetingology: help Owner
[04:17] <meetingology> menn0: Error: There is no command "owner". However, "Owner" is the name of a loaded plugin, and you may be able to find its provided commands using 'list Owner'.
[04:17] <menn0> meetingology: list Owner
[04:17] <meetingology> menn0: announce, defaultcapability, defaultplugin, disable, enable, flush, ircquote, load, logmark, quit, reload, reloadlocale, rename, unload, unrename, and upkeep
[04:41] <thumper> davecheney, axw, menn0: https://github.com/juju/mutex/pull/1
[04:42] <menn0> thumper: will look later. i've got to pick up my daughter from drama class.
[04:42] <thumper> kk
[04:43]  * davecheney looks
[04:43] <cherylj> hey axw - got a sec for a bug question?
[04:43] <axw> cherylj: yup
[04:44] <cherylj> I'm looking at bug 1592887, and the behavior the reporter is describing is what I would expect to happen
[04:44] <mup> Bug #1592887: juju destroy-service deletes openstack volumes <juju-core:New> <https://launchpad.net/bugs/1592887>
[04:44] <cherylj> wanted to sanity check
[04:45] <axw> thumper: https://github.com/juju/mutex/blob/192dc9c6d06c8353820d24757b3ed3150ccbae6c/impl_flock.go  <-- it's probably a good idea to say in the docs that a name is scoped to user ... but really I don't think we shold do that. that's different behaviour to the other implementations
[04:45] <axw> thumper: the caller can always put $USER in the name if they want to
[04:45] <axw> cherylj: looking
[04:45] <thumper> I think that could be fine
[04:45] <cherylj> thx
[04:46] <thumper> axw: there is a PR there
[04:46] <thumper> it can have comments :)
[04:46] <axw> cherylj: expected behaviour. there was always an intention of adding support for disassociating volumes from the lifetime of a service, but never fully implemented
[04:47] <cherylj> thanks, axw!
[04:51] <cherylj> does anyone know if there's an equivalent json tag for yaml's 'inline'?
[04:53] <thumper> axw, davecheney, menn0: I'll let you argue for a bit about the minor details, but I'm -1 on adding panics
[04:53]  * thumper is heading to BJJ
[05:06] <mup> Bug #1592832 changed: enable-ha embeds ModelCommand but should be controller-specific <juju-core:New> <https://launchpad.net/bugs/1592832>
[05:06] <mup> Bug #1592887 changed: juju destroy-service deletes openstack volumes <juju-core:Invalid> <https://launchpad.net/bugs/1592887>
[05:15] <wallyworld> axw: found another problem if i have a clouds.yam with a custom lxd cloud, validating initialization args: validating cloud credentials: credential "" with auth-type "empty" is not supported (expected one of [])
[05:15] <axw> le sigh
[05:16] <axw> wallyworld: we should check for empty AuthTypes list as well as one that includes "empty"
[05:16] <wallyworld> yeah, that sounds ok doesn't it
[05:16] <axw> wallyworld: you can have auth-types: ["empty"]
[05:16] <axw> but we should relax that
[05:16] <wallyworld> sgtm, cover all cases
[05:18] <axw> wallyworld: currently knee deep in adding cloud tests, can you please file a bug if you're not looking to fix it
[05:18] <wallyworld> sure, will probs just chuck up a quick fix
[05:19] <axw> wallyworld: state/cloudcredentials.go is one place to fix, not sure if there are others
[05:19] <wallyworld> yup, i'll test manually
[06:02] <axw> wallyworld: http://reviews.vapour.ws/r/5073/diff/# -- why has bundlechanges changed?
[06:03] <wallyworld> axw: they merge the service->app rename PR and so we now pull from master and not the feature branch
[06:03] <wallyworld> same code
[06:03] <axw> ok
[06:07] <wallyworld> axw: this fixed immediate issue but now i get a "model already exists" error, need to investigate that http://reviews.vapour.ws/r/5081/
[06:08] <axw> wallyworld: failed txn assertion when adding a model
[06:08] <axw> wallyworld: the error is misleading, basically means the assertions are invalid
[06:08] <wallyworld> rightio, so fix not perfect :-)
[06:08] <axw> wallyworld: did you pull master?
[06:08] <wallyworld> yup
[06:10] <axw> wallyworld: you need to not add empty to the requiredAuthTypes below
[06:10] <axw> wallyworld: well really it should be an assertion of  len(auth-types)==0 || includes "empty"
[06:11] <wallyworld> ok, wasn't sure about adding or not
[06:11] <axw> wallyworld: perhaps it would be simpler if we just require that all clouds have a non-empty AuthTypes
[06:11] <axw> wallyworld: and when we bootstrap we add []{"empty"] if there's nothing
[06:12] <wallyworld> that sounds like a bit of a pita when defining clouds
[06:12] <wallyworld> i'll make this quick fix now and we cn take a view
[06:12] <axw> wallyworld: no, we'll just add one on the way in
[06:12] <axw> wallyworld: rather than complicating the assertions everywhere else
[06:12] <wallyworld> ah, right, i see
[06:13] <wallyworld> i'll try that
[06:47] <wallyworld> axw: pushed fix to add auth types at bootstrap, seems to work
[06:47] <axw> wallyworld: thanks, still going through your other one
[06:48] <wallyworld> axw: np, sorry, it's large in scope. this other one though is a few lines - i'd like to get it landed asap if possible
[06:48] <wallyworld> so we can get CI done for  release
[06:51] <axw> wallyworld: reviewed
[06:51] <axw> (the small one)
[06:51] <wallyworld> ta
[07:05] <axw> wallyworld: reviewed the other one too
[08:17] <wallyworld> axw: thanks for reviews,  was otp so missed them. about to head to soccer. the latest commit to master is in CI now (the empty creds one). but the one before which should have had all manual / lxd fixes looks to be failing on manual still http://reports.vapour.ws/releases/4061
[08:18] <wallyworld> axw: can you take a look and fix any issue, i'll check back in after soccer; needless to say if there is an issue we need a fix asap
[08:36] <Yash> Hello
[08:36] <Yash> I'm facing a problem.
[08:36] <Yash> 2016-06-16 08:36:27 DEBUG juju.api apiclient.go:500 error dialing "wss://[fd4f:23ae:5d73:5c67:216:3eff:febc:8b38]:17070/model/3923551f-dcf9-4ca8-8b32-dc010722721b/api", will retry: websocket.Dial wss://[fd4f:23ae:5d73:5c67:216:3eff:febc:8b38]:17070/model/3923551f-dcf9-4ca8-8b32-dc010722721b/api: dial tcp [fd4f:23ae:5d73:5c67:216:3eff:febc:8b38]:17070: getsockopt: connection refused
[08:37] <Yash> How to solve this?
[08:37] <Yash> I rebooted my machine many times with no luck
[09:07] <voidspace> frobware: dimitern: standup
[09:08] <davecheney> Yash: it looks like your machine is trying to reach that host on ipv6 but either the juju server isn't listening on ipv6 or its blocked
[09:14] <Yash> ok
[09:14] <Yash> I disabled ufw
[09:15] <Yash> Is that a problem?
[09:15] <Yash> I pinf ipv6 address but not that port
[09:15] <Yash> nmap failed to connect
[09:18] <Yash> davecheney : Please suggest how to solve?
[09:23] <axw> wallyworld: the issue is that https://bazaar.launchpad.net/~juju-qa/+junk/cloud-city/view/head:/clouds.yaml contains an entry called "manual"
[09:23] <axw> which does not have any regions
[09:23] <axw> wallyworld: it was working before by luck, not by design
[09:24] <voidspace> babbageclunk: buy this and I'll buy one (or two) off you http://www.ebay.co.uk/itm/252426716669?_trksid=p2060353.m1438.l2649&ssPageName=STRK%3AMEBIDX%3AIT
[09:24] <axw> wallyworld: we only do the auto-detect thing if there's no cloud with the given name
[09:30] <babbageclunk> voidspace: They just seem like the ground effect lights that boy-racers put on their car so they can drive around the square in Palmerston North.
[09:31] <babbageclunk> babbageclunk: But for your living room!
[09:31] <babbageclunk> Gah, dumb brain.
[09:31] <dimitern> pimping up your living room? :)
[09:31] <babbageclunk> dimitern: exactly
[09:32] <babbageclunk> Yash: What does sudo lxc list show?
[09:32] <babbageclunk> Yash: Does that container have an ipv4 address as well, or just an ipv6 one?
[09:36] <babbageclunk> Something I said?
[09:36] <admcleod> maybe he's from palmerston north
[09:36] <dimitern> :)
[09:37]  * babbageclunk lols
[09:40] <admcleod> babbageclunk: thanks for that
[09:41] <babbageclunk> admcleod: Well, I don't think I was much help. Hopefully they come back.
[09:41] <axw> mgz, sinzui, balloons: can one of you please remove the "manual" entry in https://bazaar.launchpad.net/~juju-qa/+junk/cloud-city/view/head:/clouds.yaml  -- it's interfering with the ability to use the manual/<host> syntax in bootstrap
[09:45] <babbageclunk> dimitern, voidspace: Go testing question - when I run go test ./... at the top level, am I right to think that each of the packages' tests are run as separate processes?
[09:46] <babbageclunk> If I did something in juju/testing/mgo.go:init(), it would still run multiple times across the whole test suite.
[09:48] <dimitern> babbageclunk: go test ./... just recurses into each subdir, doing the same it does otherwise - i.e. build a <pkg>.test binary in a subdir then run it
[09:48] <admcleod> babbageclunk: how did you get your canonical hostname irc cloak?
[09:49] <babbageclunk> dimitern: Ok, thanks - that's what I thought.
[09:50] <admcleod> or, anyone
[09:50] <babbageclunk> admcleod: ? They asked me what irc name I wanted when I was joining.
[09:50] <admcleod> hrm ok
[09:50] <babbageclunk> admcleod: Hang on - what do you mean irc cloak?
[09:50] <dimitern> admcleod: he's in bluefin, but otherwise do a full-text search on wiki.c.c for "cloak"
[09:50] <dimitern> admcleod: there's a separate process for freenode and canonical IIRC
[09:51] <admcleod> dimitern: yeah nothing on the wiki that i can find
[09:51] <admcleod> babbageclunk: when you whois someone, what should be their hostname/ip address is cloaked/hidden
[09:51] <dimitern> https://wiki.canonical.com/StayingInTouch/IRC/FreeNodeRegistration?highlight=%28cloak%29
[09:51] <admcleod> clearly i dont know how to use the search box
[09:51] <admcleod> thanks :)
[09:51] <dimitern> ;)
[09:53] <dimitern> babbageclunk: a cloak can mask your source address for /whois on IRC
[09:53] <admcleod> dimitern: oh right. enter does a title search.
[09:53] <babbageclunk> admcleod: <reads> I don't think I have one.
[09:54] <dimitern> babbageclunk: you do :) all bluefin folk have one by default
[09:54] <admcleod> babbageclunk: [babbageclunk] (user@nat/canonical/x-zxxacbyqsikrawst)
[09:54] <babbageclunk> admcleod, dimitern: ah. cool!
[10:00] <admcleod> babbageclunk: i believe kjackal may have a question for you also
[10:00] <kjackal> hi babbageclunk
[10:00] <babbageclunk> kjackal: hi!
[10:00] <kjackal> I am on juju beta8
[10:01] <kjackal> http://pastebin.ubuntu.com/17393462/
[10:01] <kjackal> Deployed a machine (with kafka but that does not matter) and the fqdn is not resolvable/pingable
[10:02] <kjackal> is this expected?
[10:02] <babbageclunk> kjackal: What are you deploying to?
[10:02] <kjackal> solly yes, lxd
[10:02] <kjackal> sorry
[10:02] <babbageclunk> kjackal: realised that after looking at the pastebin, sorry.
[10:03] <admcleod> kjackal: nslookup is dns server specific, it doesnt look at /etc/hosts
[10:03] <kjackal> admcleod: yes true!
[10:04] <babbageclunk> kjackal: I'm not sure whether we'd expect the container to be resolvable. dimitern?
[10:04] <kjackal> Actually! After sometime it gets resolvable and pingable!
[10:04] <babbageclunk> kjackal: What's the broader problem?
[10:04] <kjackal> http://pastebin.ubuntu.com/17393499/
[10:05] <babbageclunk> Yash: welcome back! Did you see my question above?
[10:05] <kjackal> So, the fqdn is not resolvable immediately after the container comes up
[10:05] <kjackal> babbageclunk: ^
[10:06] <babbageclunk> kjackal: Sure - but is that actually causing a problem?
[10:07] <kjackal> babbageclunk: Yes because if i try to start immediately after I get the machine a service (in my case kafka) it will fail because all the handshakes with other services will fail and in the case of kafka the fqdn is used internaly for figuring out the interfaces to listen to
[10:07] <Yash> no
[10:07] <babbageclunk> kjackal: (I mean, it might be, but I just want to know what the context is - what's the problem you're trying to solve?)
[10:08] <Yash> babbageclunk: Now I cleaning machine. :(
[10:08] <babbageclunk> 10:32 <babbageclunk> Yash: What does sudo lxc list show?
[10:08] <babbageclunk> > 10:32 <babbageclunk> Yash: Does that container have an ipv4 address
[10:08] <babbageclunk> Yash: :(
[10:09] <Yash> 10 machines with ip4 and ipv6 ips
[10:09] <Yash> all are running
[10:09] <babbageclunk> kjackal: Ah, ok - thanks
[10:09] <kjackal> my exact problem: starting kafka without its fqdn resolvable fails throwing an unknown host exception
[10:09] <Yash> I cann't ssh ubuntu@publicip
[10:09] <Yash> connetion refused
[10:10] <kjackal> also I think that if I have two services (eg kafka and zookeeper) trying to comunicate using their fqdns will fail
[10:10] <kjackal> babbageclunk: ^
[10:11] <babbageclunk> kjackal: Sorry, I don't think I'm the right person to answer this (I'm a newbie here). dimitern, any ideas?
[10:12] <kjackal> babbageclunk: I appreciate your help
[10:13] <babbageclunk> kjackal: Wish I could be more helpful!
[10:20] <babbageclunk> Yash: so you get connection refused from ssh, rather than permission denied?
[10:26] <dimitern> kjackal, babbageclunk: sorry, was afk for a bit
[10:27] <dimitern> kjackal, babbageclunk: it looks like either a lxd issue or juju-using-lxd-incorrectly I guess
[10:27] <dimitern> kjackal: what's inside /etc/resolv.conf inside the container?
[10:28] <kjackal> just a sec
[10:28] <dimitern> kjackal: it might be relevant whether this is a trusty or xenial container..
[10:28] <babbageclunk> Yash: Can you get into the container using "sudo lxc exec <container-name> -- /bin/bash"?
[10:29] <kjackal> dimitern: http://pastebin.ubuntu.com/17393776/
[10:30] <dimitern> kjackal: ok, that looks good - do you have another lxd that cannot resolve itself?
[10:30] <kjackal> I have to spin up a new one
[10:30] <kjackal> what do you want me to check there?
[10:30] <kjackal> the resolv.conf?
[10:31] <dimitern> kjackal: yeah, and also pinging e.g. google.com
[10:31] <kjackal> dimitern: ^
[10:31] <kjackal> Ok doing it now, will ping you in a moment
[10:31] <dimitern> kjackal: btw the /etc/hosts does not have lxd's own hostname.. grr looks like bug 1513165 but on lxd rather than maas
[10:31] <mup> Bug #1513165: Containers registered with MAAS use wrong name <cdo-qa-blocker> <sts> <sts-needs-review> <juju-core:Fix Released by thumper> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1513165>
[10:32] <dimitern> kjackal: just to clarify - what version of juju are you using?
[10:32] <kjackal> 2.0-beta8-xenial-amd64
[10:33] <dimitern> kjackal: can you please file a bug like the above, so we can track it separately?
[10:34] <kjackal> yes I will do that
[10:34] <dimitern> kjackal: please include a paste with /etc/hosts, /etc/resolv.conf, and /etc/network/interfaces, ideally for a container that works ok (like that one above) and a not working one
[10:35] <dimitern> kjackal: thank you!
[10:35] <kjackal> the ubuntu lxd container came up fine
[10:36] <dimitern> kjackal: :/ yeah.. it looks like one of those lxd race conditions..
[10:36] <kjackal> dimitern: here is what I got this time http://pastebin.ubuntu.com/17393827/
[10:36] <kjackal> and is resolvable immediatelly
[10:37] <kjackal> cool, let me file this bug and i will try again to repro, to see what the resolv.conf is
[10:37] <dimitern> kjackal: ok, try deploying the charm that had the issue I guess?
[10:37] <dimitern> kjackal: awesome! thanks, and sorry for the issues :/
[10:37] <kjackal> yes, that is the plan. Do not mention it, this is why we are here for
[10:39] <dimitern> kjackal: hey, I've just "groked" your nick btw :) - how's the provider going?
[10:39] <kjackal> :) "how is it going" in what sence
[10:39] <kjackal> ?
[10:40] <dimitern> kjackal: we should try and help you guys with any issues along the way.. it's a bit of a rough path, but you're trailblazers :)
[10:40] <dimitern> kjackal: well, I've been looking the ML for progress
[10:40] <dimitern> just curious
[10:42] <kjackal> dimitern: I am looking at bug https://bugs.launchpad.net/juju-core/+bug/1513165
[10:42] <mup> Bug #1513165: Containers registered with MAAS use wrong name <cdo-qa-blocker> <sts> <sts-needs-review> <juju-core:Fix Released by thumper> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1513165>
[10:42] <kjackal> in the lxd case both juju-095f51-2.lxd and juju-095f51-2 are resolvable
[10:43] <kjackal> dimitern: Should I still open a bug?
[10:43] <dimitern> so the dnsmasq instance listening on lxdbr0 is handling DNS requests
[10:44] <dimitern> kjackal: yes please, esp. if you find a way to reproduce the issue
[10:45] <kjackal> they are both pingable http://pastebin.ubuntu.com/17393893/ but we also need the /etc/hosts to include the fqdn
[10:48] <dimitern> kjackal: yeah, sounds like https://bugs.launchpad.net/charms/+source/rabbitmq-server/+bug/1574844
[10:48] <mup> Bug #1574844: juju2 gives ipv6 address for one lxd, rabbit doesn't appreciate it. <conjure> <juju-release-support> <landscape> <lxd-provider> <juju-core:Won't Fix> <rabbitmq-server (Juju Charms Collection):Fix Released by james-page> <https://launchpad.net/bugs/1574844>
[10:49] <dimitern> kjackal: not quite, but the same issue - not having the lxd's address and hostname in /etc/hosts
[10:50] <dimitern> kjackal: so filing a bug about this will be appreciated!
[10:54] <kjackal> here you go dimitern https://bugs.launchpad.net/juju-core/+bug/1593185
[10:54] <mup> Bug #1593185: In lxd the containers own fqdn is not inclused in /etc/hosts <juju-core:New> <https://launchpad.net/bugs/1593185>
[10:55] <dimitern> kjackal: thank you!
[10:58] <kjackal> dimitern: how is it different from deploying a local charm from fetching it from the store in terms of name resolutions, could this be related
[10:58] <kjackal> I deployed my test kafka charm from local and is not resolved...
[10:58] <dimitern> kjackal: it shouldn't matter where the charm comes from
[10:58] <kjackal> ah wait, I am deploying in trusty series!
[10:59] <kjackal> let me try deploying ubuntu from the store trusty series
[11:02] <kjackal> I think we have found something dimitern, ubuntu trusty series not resolvable
[11:03] <dimitern> kjackal: with a local charm though, you *could* use a similar workaround jamespage did for rabbitmq-server - i.e. update /etc/hosts to include a line with the IP address (returned by `unit-get private-address` in the charm) and the `hostname` (short and fqdn)
[11:03] <kjackal> nameserver <IP_ADDRESS>
[11:03] <dimitern> kjackal: no search?
[11:03] <kjackal> search lxd
[11:04] <kjackal> dimitern: this kind of workaround is not good, because the hostname has to be resolvable by both itself and by others!
[11:04] <dimitern> kjackal: what does `nslookup juju-xxx.lxd <IP_ADDRESS>` return?
[11:05] <kjackal> http://pastebin.ubuntu.com/17394126/
[11:05] <dimitern> kjackal: and with the .lxd suffix?
[11:06] <kjackal> same
[11:06] <dimitern> kjackal: odd.. can you ping the dns ip?
[11:07] <kjackal> yes <IP_ADDRESS> is pingable
[11:07] <dimitern> kjackal: also, can you paste the output of `ip -d route show` ?
[11:08] <kjackal> http://pastebin.ubuntu.com/17394152/
[11:09] <dimitern> kjackal: ok, I suspect there might be a lingering `dhclient` process on eth0 due to /etc/network/interfaces.d/eth0.cfg being present..
[11:09] <dimitern> kjackal: can you please paste /etc/network/interfaces on the container?
[11:10] <mup> Bug #1593185 opened: In lxd the containers own fqdn is not inclused in /etc/hosts <juju-core:New> <https://launchpad.net/bugs/1593185>
[11:10] <mup> Bug #1593188 opened: Include complete information in Client.CharmInfo API call <blocker> <juju-core:In Progress by frankban> <https://launchpad.net/bugs/1593188>
[11:10] <kjackal> Yes there is a process http://pastebin.ubuntu.com/17394175/
[11:10] <kjackal> dimitern: ^
[11:10] <kjackal> http://pastebin.ubuntu.com/17394184/
[11:11] <kjackal> dimitern: the interfaces ^
[11:11] <dimitern> kjackal: yeah :/ I suspect you'll have better outcome with a more recent version than beta8, e.g. from the daily ppa
[11:12] <kjackal> awesome! there is an issue already resolved?
[11:13] <dimitern> kjackal: that one with eth0.cfg messing up things should be, not the missing /etc/hosts line
[11:13] <dimitern> kjackal: but unfortunately the daily ppa seems out of date - last build was on June, 8, so it won't have the fix
[11:14] <kjackal> Beta 9 should have the fix right?
[11:14] <dimitern> kjackal: would you mind trying to build juju from source?
[11:14] <dimitern> yeah, once it's out - which, I'm told should be by end of this week
[11:15] <kjackal> dimitern: Ah I always wanted to do that!!! (compile from sources)
[11:15] <kjackal> going to grab something to eat and will start after that, ok?
[11:15] <dimitern> kjackal: ok! always good to have early feedback :)
[11:16] <dimitern> kjackal: ok, try to follow the steps in the README.md on https://github.com/juju/juju
[11:16] <dimitern> I'll help if needed
[11:24] <dimitern> babbageclunk: can you open LKK now?
[11:24] <dimitern> babbageclunk: ah, sorry - it's back up apparently
[11:25] <wallyworld> axw: thanks for investigating, i'll send an email
[12:11] <perrito666> morning
[12:15] <voidspace> perrito666: morning
[12:15] <voidspace> perrito666: what country are you in?
[12:15] <perrito666> voidspace: argentina, why?
[12:16] <voidspace> perrito666: ah, there's a chance I might be visiting Brasil later this year and I couldn't remember if you were Brasil or Argentina
[12:16] <voidspace> sorry :-)
[12:16] <perrito666> I am actually on a bus traveling from my city to a much smaller city
[12:17] <voidspace> sounds like fun
[12:17] <voidspace> why?
[12:18] <perrito666> well some family issues (and also an excelent chance to stress test my lte modem)
[12:19] <voidspace> perrito666: ah, sorry about the family issues
[12:22] <fwereade> perrito666, wallyworld, if you're both around: can you talk me through the two collections it looks like we'll be using?
[12:24] <babbageclunk> perrito666: Want to test your modem with a review? (It's the Mongo version detection.) http://reviews.vapour.ws/r/5084/
[12:24] <babbageclunk> perrito666: (Hope the family is ok)
[12:25] <perrito666> babbageclunk: going, family is ok, just annoying :p
[12:26] <babbageclunk> perrito666: Oh good. Mine too!
[12:28] <wallyworld> fwereade: modeluser collection is from the initial multi-model work - it is like a sql join table between models and users. the permissions collection records an access privilege for a user on a target (model/controller)
[12:34] <fwereade> wallyworld, how does the latter not encompass the former?
[12:34] <fwereade> wallyworld, I'm all for the perms collection, but I think it renders modelusers redundant
[12:35] <wallyworld> the former is who can access a model at some level. the permissions collection is generic and used to record permissions on various targets (controller, model) for various source entities (users, groups)
[12:36] <wallyworld> modelusers records things like last access time etc (from memory)
[12:36] <wallyworld> not permission related
[12:39] <fwereade> wallyworld, ok, so we're dropping Access from modeluser? and requiring that we create a perms doc for each modeluser?
[12:39] <wallyworld> yep
[12:39] <fwereade> wallyworld, ok, thanks, makes sense now, sorry
[12:39] <fwereade> perrito666, ^^
[12:40] <wallyworld> separation of concerns and all that
[12:40] <wallyworld> and separate mongo docs to avoid write locks
[12:40] <fwereade> wallyworld, yeah, absolutely
[12:40] <fwereade> wallyworld, tyvm
[12:40] <perrito666> ok, you saved me the explanation tx :)
[12:40] <wallyworld> np, glad we got the design right :-)
[12:40] <fwereade> wallyworld, I had it in my mind that last-connand stuff were elsewhere
[12:40] <fwereade> cheers
[12:41] <wallyworld> thanks for asking the question, always good to be sure
[12:43] <kjackal> Hey dimitern, it seems the problem still exists in juju beta 9
[12:44] <kjackal> I compiling from source juju still results in unresolvable fqdns in trusty containers
[12:46] <dimitern> kjackal: how about dhclient - is it still there?
[12:47] <kjackal> yes it is still here :(
[12:47] <dimitern> kjackal: and can you paste the /etc/network/interfaces?
[12:49] <kjackal> dimitern: http://pastebin.ubuntu.com/17395368/ at the very bottom
[12:51] <kjackal> you were suspecting this would be fixed right? do we have a ticket for me to read so that I understand what is happening? If I understand this correctly dhcp handshake hungs and therefore the nameresolution service on the host is not updating its entries
[12:51] <dimitern> kjackal: ok, that's not good - did you bootstrap with --upload-tools ?
[12:52] <kjackal> dimitern: yes http://pastebin.ubuntu.com/17395425/
[12:53] <sinzui> axw wallyworld Do we still need remove manual from clouds.yaml to mark bug 1593033 fix released?
[12:53] <mup> Bug #1593033: manual: bootstrapping fails with "creating hosted model: model already exists" <blocker> <juju-core:Fix Committed by axwalk> <https://launchpad.net/bugs/1593033>
[12:53] <dimitern> kjackal: the stanza 'source etc/network/interfaces.d/*.cfg' pulls in that eth0.cfg causing the dhclient to come up and acquire a DHCP lease, even if there's already a static address for eth0
[12:53] <wallyworld> sinzui:  that bug is a different root cause, the manual in clouds causes CI failures
[12:54] <wallyworld> the root cause for that bug should be fixed
[12:54] <sinzui> wallyworld: okay, I report a separate bug for clouds.yaml
[12:54] <voidspace> dimitern: babbageclunk: actually turned out to be easy to test
[12:54] <voidspace> dimitern: babbageclunk: http://reviews.vapour.ws/r/5085/
[12:54] <wallyworld> sinzui: ok, and if we retest the manual deployments, it should work with manual removed
[12:55] <dimitern> kjackal: hmm, can you check what's the commit hash in $GOPATH/src/github.com/juju/juju/ ?
[12:55] <dimitern> git log -n1 in there..
[12:56] <dimitern> voidspace: cheers, will have a look shortly
[12:57] <kjackal> dimitern: http://pastebin.ubuntu.com/17395483/
[12:58] <dimitern> kjackal: if you try running `go install -v github.com/juju/juju/...` does it rebuild anything?
[12:59] <dimitern> kjackal: it's also worth noting the first jujud binary in $PATH (`which jujud`) will be uploaded with --upload-tools, and it might be not the one you built but the system-wide one from the package
[13:02] <kjackal> dimitern: the jujud binary: /home/jackal/workspace/gogogo/bin/jujud
[13:02] <kjackal> dimitern: go install -v github.com/juju/juju/... did not build anything
[13:03] <dimitern> kjackal: ok, just wanted to double check the binary is correct..
[13:04]  * dimitern *facepalms*
[13:04] <dimitern> kjackal: sorry, I forgot the issue I was thinking about is fixed, but for containers on maas provider and others, not the lxd provider
[13:05] <dimitern> kjackal: so, it's not fixed, but we'll get to it soon
[13:06] <kjackal> dimitern: do we have a ticket we can monitor. We have a couple of charms that we will need to review as soon as this issue is resolved
[13:08] <dimitern> kjackal: yeah - that one you filed is already triaged as high and affecting 1.25 and master
[13:10] <perrito666> bbl
[13:11] <kjackal> So you are saying is I add the hostname in the hosts file all will be well?
[13:16] <kjackal> dimitern: I do not understand the mechanism, but I trust you
[13:16] <kjackal> thanks
[13:18] <dimitern> kjackal: well, assuming inside the container eth0 has IP <IP_ADDRESS>, if you add a line `<IP_ADDRESS>  juju-767941-0 juju-767941-0.lxd` in /etc/hosts after the line about <IP_ADDRESS>, resolving should work inside the container
[13:19] <mup> Bug #1593221 opened: remove manual from clouds.yaml <juju-core:Fix Committed by sinzui> <https://launchpad.net/bugs/1593221>
[13:19] <kjackal> yes, from within the container resolving the juju-767941-0.lxd would work. However will that fqdn be resolvable from others?
[13:22] <kjackal> dimitern: Kafka talks to Zookeeper and says "Hey zookeeper, I am a new kafka unit so that you know I am juju-767941-0.lxd", then Zookeeper talks to Kafka and says "Nah, you are nobody, I cannot find you on DNS"
[13:24] <dimitern> kjackal: so long as both kafka and zookeeper use the same dns server, and the server works, it should be fine
[13:25] <dimitern> kjackal: the issue is the dnsmasq seems to not recognize the hostnames we set inside the container
[13:25] <kjackal> dimitern: ok, thank you!
[13:25] <dimitern> hmm... that's the real problem
[13:26] <dimitern> kjackal: can you compare what you see as hostname in /etc/hostname and in /var/log/cloud-init-output.log during the initial boot in the container?
[13:29] <kjackal> what am I searching for in cloud-init-output?
[13:29] <kjackal> I can see The key fingerprint is:
[13:29] <kjackal> 35:24:ce:24:69:5b:89:d5:76:35:51:ab:67:1b:88:57 root@juju-767941-2
[13:29] <dimitern> kjackal: search for 'hostname' - from the top I guess
[13:30] <kjackal> the "juju-767941-2" is the /etc/hostname
[13:30] <dimitern> kjackal: either in /v/l/cloud-init-output.log, or in /v/l/cloud-init.log (where it says as it's about to configure each bit)
[13:31] <dimitern> kjackal: ah, maybe easier - check /var/lib/cloud/ - rgrep for "hostname:" ?
[13:32] <kjackal> dimitern: cc_set_hostname.py[DEBUG]: Setting the hostname to juju-767941-2.localdomain (juju-767941-2)
[13:32] <dimitern> kjackal: that's it!
[13:33] <dimitern> kjackal: but I bet `nslookup juju-767941-2.localdomain` doesn't resolve?
[13:34] <kjackal> dimitern:  nope, it does not resolve
[13:35] <dimitern> kjackal: ok, thanks - added a comment about that to the bug as it looks like the real cause
[13:37] <kjackal> thanks
[13:48] <dimitern> voidspace: reviewed
[14:23] <voidspace> dimitern: ta
[14:28] <mup> Bug #1593221 changed: remove manual from clouds.yaml <juju-core:Fix Released by sinzui> <https://launchpad.net/bugs/1593221>
[14:37] <mup> Bug #1593221 opened: remove manual from clouds.yaml <juju-core:Fix Released by sinzui> <https://launchpad.net/bugs/1593221>
[14:41] <fwereade> whoa, why are we erasing status history for removed units?
[14:41] <fwereade> perrito666, ^^
[14:42] <fwereade> not even for *removed* units, merely *destroyed* units
[14:43] <perrito666> fwereade: we.. good question, I think we deemed it proper cleanup
[14:43] <perrito666> but I am sure you disagree
[14:44] <fwereade> perrito666, I do think it's a misleading use of the word "history"
[14:45] <fwereade> perrito666, and apart from anything else the unit will still be setting statuses and recording history as it shuts down, won't it?
[14:51] <perrito666> fwereade: agree, open abug pls
[14:51] <Yash> Hello dimitern
[14:52] <Yash> I'm facing a problem. 14         pending <IP_ADDRESS> juju-4667c953-1492-4846-8123-071efb515fe4-machine-14 xenial
[14:52] <Yash> 14         pending <IP_ADDRESS> juju-4667c953-1492-4846-8123-071efb515fe4-machine-14 xenial
[14:52] <Yash> Machine is in pending state
[14:52] <mup> Bug #1593221 changed: remove manual from clouds.yaml <juju-core:Fix Released by sinzui> <https://launchpad.net/bugs/1593221>
[14:52] <Yash> can we start it?
[14:58] <mup> Bug #1593263 opened: juju deploy openstack-base results in error with ceph-mon <juju-core:New> <https://launchpad.net/bugs/1593263>
[15:02] <dimitern> Yash: hey, I'd check the maas ui to see what's keeping it up? or is this lxd?
[15:28] <babbageclunk> Yash: terminal only?
[15:29] <babbageclunk> Yash: It's a way of getting onto the machine that doesn't rely on ssh (handy if the network isn't coming up).
[15:29] <Yash> I mean is it I'm inside running machine
[15:29] <Yash> virtual machine
[15:29] <Yash> ok
[15:30] <Yash> server is down ..I can see no server running
[15:30] <Yash> ss -t -a
[15:31] <babbageclunk> so to remind myself - you've bootstrapped to LXD? And the controller is stuck in pending?
[15:31] <babbageclunk> Or another machine?
[15:31] <Yash> Hey babbageclunk restarting machine 0 brings server back
[15:31] <Yash> I can see status now
[15:31] <babbageclunk> Yash: yay - when you say server do you mean the juju controller?
[15:31] <Yash> but one unit is showing agent is lost, sorry! See 'juju status-history neutron-api
[15:32] <babbageclunk> Yash: sometimes after rebooting it takes a while for things to get restarted and reconnected.
[15:32] <Yash> Problem is when I try to deploy openstack one by one components.. (openstack bundle never works for me)
[15:33] <Yash> Suddenly one machine never starts and remain in pending state
[15:33] <Yash> so I restart / sometimes remove server with force machine removal
[15:34] <Yash> Now can you please help me what is this error
[15:34] <Yash> agent is lost, sorry! See 'juju status-history neutron-a
[15:34] <Yash> -api
[15:34] <babbageclunk> Yash: in juju status, does that machine show up with an ipv6 address as its public address?
[15:34] <babbageclunk> because we had a bug that sounds like this.
[15:34] <Yash> This time I'm not using ipv6 only ipv4
[15:35] <Yash> in lxd bridge configuration..I ignored ipv6
[15:35] <babbageclunk> Can you paste juju status to http://pastebin.ubuntu.com/
[15:35] <Yash> Ipv6 surely some problem there
[15:36] <Yash> juju status --debug
[15:36] <Yash> or ?
[15:36] <Yash> how
[15:36] <babbageclunk> Yash: yeah, we definitely had a bug with lxd containers and ipv6
[15:36] <babbageclunk> Yash: Is juju status working for you now?
[15:36] <Yash> yes
[15:37] <Yash> restarting worked..
[15:37] <babbageclunk> So could you cut and paste it into a pastebin?
[15:37] <Yash> Sure..is there any shortcut of doing...I mean command line tool or like that
[15:38] <marcoceppi> katco: did those patches for OSM/manual provider cleanup ever get released in a 1.25 release?
[15:39] <katco> marcoceppi: not to my knowledge. only in a special branch/binary.
[15:39] <Yash> http://pastebin.ubuntu.com/17399592/
[15:39] <Yash> This time it's clean
[15:39] <Yash> only agent lost
[15:39] <Yash> How can I fix that error?
[15:39] <marcoceppi> katco: cool, I'm about to reply to an email about it, testing seems positive, so I'm sure the stakeholders will want to see that in a point release sooner (rather than later). I'll email some folks about it when I get home
[15:40] <katco> marcoceppi: cool.
[15:40] <babbageclunk> Yash: awesome, thanks
[15:40] <mup> Bug #1593274 opened: remove-unit deletes (some) status history <juju-core:Triaged> <https://launchpad.net/bugs/1593274>
[15:42] <babbageclunk> Ok, so can you ssh onto machine 9?
[15:42] <Yash> http://pastebin.ubuntu.com/17399701/
[15:42] <Yash> Here we can see 106 ip machine
[15:42] <Yash> but not with juju status
[15:42] <Yash> yea..sorry we see
[15:43] <babbageclunk> Hmm - you can see the .106 machine in the machines list.
[15:43] <Yash> juju ssh 9  : failed
[15:43] <mup> Bug #1593263 changed: juju deploy openstack-base results in error with ceph-mon <juju-core:Invalid> <https://launchpad.net/bugs/1593263>
[15:44] <Yash> ssh ubuntu@ip  : connection refused
[15:44] <Yash> same error
[15:45] <Yash> This command rocks
[15:45] <Yash> sudo lxc exec juju-4667c953-1492-4846-8123-071efb515fe4-machine-9 -- /bin/bash
[15:45] <Yash> Please include somewhere in docs
[15:45] <Yash> it will everyone
[15:45] <Yash> I restarted machine..let's c
[15:45] <babbageclunk> No!
[15:45] <babbageclunk> I mean, you can do that.
[15:46] <babbageclunk> But then we can't work out what's gone wrong.
[15:46] <Yash> ok how?
[15:46] <babbageclunk> Ah well
[15:46] <Yash> now machine is back..agent lost problem solved
[15:46] <Yash> you guys rocked :)
[15:46] <babbageclunk> :)
[15:47] <babbageclunk> Don't know if we helped much - it's better if the machine comes up properly!
[15:47] <Yash> That will be awesome
[15:48] <Yash> one bug is it's really slow and I have wait unless one machine comes up then try another
[15:48] <Yash> two or more deploy create problems
[15:49] <Yash> I think it's not bug or I missing something
[15:49] <Yash> ceph-osd/0        blocked         idle        2.0-beta7 6                <IP_ADDRESS> No block devices detected using current configuration
[15:49] <Yash> No block devices detected using current configuration
[15:49] <Yash> What is this?
[15:50] <Yash> Do I need to configure something inside machine which should be automatic ? not sure though
[15:51] <babbageclunk> Not sure, but I think ceph needs block devices to provide its storage. https://jujucharms.com/docs/devel/charms-storage
[15:52] <babbageclunk> Actually, I don't know how it relates to cinder (openstack block storage)
[15:55] <Yash> ok some charms are still for trusty like
[15:55] <Yash> juju deploy cs:~axwalk/postgresql --storage data=cinder,10G
[15:55] <Yash> on devel doc which suppose to be for xenial ..Am I right?
[15:56] <mup> Bug #1593263 opened: juju deploy openstack-base results in error with ceph-mon <juju-core:Invalid> <https://launchpad.net/bugs/1593263>
[16:01] <babbageclunk> I think that doc was written before xenial was out.
[16:02] <Yash> ok
[16:04] <Yash> How to access http://<IP_ADDRESS>/gui/uuid from laptop ......when lxd is in desktop within same network
[16:04] <Yash> I mean <IP_ADDRESS> is private ip inside desktop
[16:05] <Yash> Its required for Juju gui and openstack dashboard
[16:05] <Yash> I can't find doc on this topic?
[16:05] <Yash> Please suggest?
[16:05] <babbageclunk> I use sshuttle: https://github.com/apenwarr/sshuttle
[16:06] <babbageclunk> on the laptop, run sshuttle -r user@desktop <IP_ADDRESS>/8
[16:06] <Yash> and from web broswer
[16:07] <Yash> That's cool tool
[16:07] <babbageclunk> Yeah, it's really neat.
[16:07] <babbageclunk> Once it's running you should be able to see <IP_ADDRESS> in the browser.
[16:08] <mup> Bug #1593263 changed: juju deploy openstack-base results in error with ceph-mon <juju-core:Invalid> <https://launchpad.net/bugs/1593263>
[16:08] <Yash> let me try :)
[16:08] <babbageclunk> (dimitern only put me on to it a few days ago)
[16:17] <mup> Bug #1591225 changed: Generated image stream is not considered in bootstrap on private cloud <juju-core:Opinion> <https://launchpad.net/bugs/1591225>
[16:17] <mup> Bug #1592887 opened: juju destroy-service deletes openstack volumes <juju-core:New> <https://launchpad.net/bugs/1592887>
[16:17] <mup> Bug #1593299 opened: HA recovery fails in azure <azure-provider> <blocker> <ci> <ha> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1593299>
[16:17] <mup> Bug #1593303 opened: Google Compute Engine provider often reports wrong IP address as the public address <juju-core:New> <https://launchpad.net/bugs/1593303>
[16:35] <dooferlad> dimitern, frobware: do you have an update on https://bugs.launchpad.net/maas/+bug/1590689 - just being asked myself
[16:35] <mup> Bug #1590689: MAAS 1.9.3 + Juju 1.25.5 - on the Juju controller node eth0 and juju-br0 interfaces have the same IP address at the same time <cpec> <juju> <maas> <sts> <juju-core:Fix Committed> <juju-core 1.25:In Progress by dimitern> <MAAS:Invalid> <https://launchpad.net/bugs/1590689>
[16:36] <dimitern> dooferlad: I have a working fix, but not done as it causes issues for lxcs still, but on the up side is confirmed to work with bonds ok
[16:38] <dooferlad> dimitern: thanks for the update. If you could put a quick update in the bug then anastasiamac will be very happy. Do you have an ETA?
[16:40] <dimitern> dooferlad: later tonight, will update the bug as well - need to be afk for a while though..
[16:43] <dooferlad> dimitern: please ping me for the review.
[16:43] <dimitern> dooferlad: ok
[16:44] <mup> Bug # changed: 1577945, 1589353, 1592221, 1592582, 1592981, 1592987
[16:52] <dimitern> dooferlad: here it is, for review (might need to tweak it here and there after I do more testing): http://reviews.vapour.ws/r/5087/
[16:52] <dimitern> frobware, voidspace: ^^ if you can have a look as well
[16:53] <mup> Bug # changed: 1482634, 1504637, 1537585, 1553059, 1571545, 1576318, 1576674, 1577614, 1579633, 1581627, 1581893, 1583412, 1585005, 1586298, 1587788, 1588095, 1588446, 1588559, 1588924, 1589061, 1589066, 1589748, 1590095, 1590205, 1590689, 1590960, 1592210, 1592733, 1593033, 1593042, 1593188
[16:57] <dooferlad> dimitern: so, not a small change then *sigh*
[17:04] <anastasiamac> fwereade: format 2.0 PR is pretty much just a rename of existing file. I'll remove further refs to 1.18 u've identified but do not feel like fixing yaml ouput/tags is concern of this PR :D
[17:04] <anastasiamac> fwereade: m happy to be corrected :)
[17:07] <dimitern> dooferlad: it's not huge - the important parts are in add-juju-bridge.py mostly; the other stuff is mostly backported from master (except for the state changes, which turned out to be needed)
[17:10] <voidspace> dimitern: looking
[17:15] <voidspace> dimitern: I seem to have reviewed this before...
[17:15] <dimitern> voidspace: it's mostly backported
[17:32] <Yash> Now I can see dashboard login...hurray :)
[17:32] <Yash> http://<IP_ADDRESS>/horizon/auth/login/
[17:33] <Yash> what is password  and username?
[17:33] <fwereade> anastasiamac, I would really appreciate it if you would add the tags, I feel we should be eliminating implicit serializations as we touch them
[17:39] <anastasiamac> fwereade: only because u ask so nicely and will really appreciate it \o/
[17:39] <anastasiamac> fwereade: tyvm for review :D
[17:44] <mup> Bug #1593350 opened: Juju register allows users to register alternatively named controllers of the same UUID <juju-core:In Progress by macgreagoir> <https://launchpad.net/bugs/1593350>
[17:48] <voidspace> dimitern: LGTM
[18:13] <redir> perrito666: yt?
[18:13] <redir> katco: yt?
[18:13] <katco> redir: otp, ttyl
[18:13] <perrito666> redir: yup
[18:13] <redir> perrito666: I'm back re: keystone3
[18:14] <perrito666> redir: tell me
[18:15] <redir> perrito666: https://goo.gl/d5S5mF says If "domain-name" is present (and
[18:15] <redir> user/password too) juju will use V3 authentication by default.y
[18:15] <redir> so is that present as a key or present as a non empty string?
[18:15] <redir> perrito666: ^
[18:15] <redir> hapy to HO if htat is easier
[18:16] <perrito666> as a non empty string
[18:16] <perrito666> redir: I am in a place where I could not ho properly, apologies
[18:16] <redir> tx
[18:16] <redir> np perrito666
[18:16] <perrito666> redir: I did the original of that and katco did an amazin job fixing it because I had dome some dumb things
[18:20] <mup> Bug #1592155 changed: restore-backup fails when attempting to 'replay oplog'. <backup-restore> <blocker> <juju-core:Fix Released> <https://launchpad.net/bugs/1592155>
[18:23] <mup> Bug #1592155 opened: restore-backup fails when attempting to 'replay oplog'. <backup-restore> <blocker> <juju-core:Fix Released> <https://launchpad.net/bugs/1592155>
[18:27] <dimitern> voidspace: thanks!
[18:32] <mup> Bug #1592155 changed: restore-backup fails when attempting to 'replay oplog'. <backup-restore> <blocker> <juju-core:Fix Released> <https://launchpad.net/bugs/1592155>
[18:50] <mup> Bug #1579750 changed: Wrong hostname added to dnsmasq using LXD <lxd-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1579750>
[19:05] <dooferlad> cherylj, anastasiamac, macgreag1ir, redir: http://paste.ubuntu.com/17408402/
[19:19] <redir> perrito666: http://reviews.vapour.ws/r/5088/
[19:20] <redir> katco: perrito666 ^ can you have a look? That makes the warning go away, but unsure if other bits were lost along the way
[19:50] <mup> Bug #1593394 opened: model already exists but can't be destroyed because it's not found <v-pil> <juju-core:New> <https://launchpad.net/bugs/1593394>
[19:50] <mup> Bug #1593395 opened: model already exists but can't be destroyed because it's not found <v-pil> <juju-core:New> <https://launchpad.net/bugs/1593395>
[20:21] <mup> Bug #1593395 changed: model already exists but can't be destroyed because it's not found <v-pil> <juju-core:New> <https://launchpad.net/bugs/1593395>
[22:05] <perrito666> this make sno sense, the whole trip coming to this city I had LTE and now returning from I only have 3g
[22:05] <perrito666> oh there it is
[22:06] <perrito666> wallyworld: wanna?
[22:06] <wallyworld> sure
[22:06]  * katco has been forced to retreat to her headless to run the full suite of juju tests
[22:06] <perrito666> wallyworld: loading
[22:21] <alexisb_> wallyworld, available whenever you are free
[22:21] <wallyworld> alexisb_: be there in a minute, just talking to horatio
[22:22] <alexisb_> perrito666 I love all teh different variations of you name wallyworld comes up with
[22:24] <perrito666> wallyworld: sorry went from LTE to Edge
[22:24] <wallyworld> perrito666: np, i think we had finished
[22:25] <wallyworld> enjoy the rest of the bus trip back home :-)
[22:25] <perrito666> alexisb_: he usually goes very close to hora[a-z]*o
[22:25] <perrito666> wallyworld: yes, people seems rather unhappy that I awoke them by speaking english loudly :p
[22:26] <wallyworld> :-)
[22:26] <perrito666> I still cant understand how this same trip this morning had LTE coverage and now it hasnt
[22:26] <perrito666> and honestly, who sleeps in a 6pm trip?
[23:56] <thumper> axw, davechen1y, menn0: I have updated the juju/mutex PR, keeping the Acquirer interface, but removing Acquire function to have only one way. Renamed Spec to Mutex, removed error return from Release
[23:56] <thumper> tested on linux, mac and windows
[23:56] <thumper> also added a few more tests
[23:58] <thumper> davechen1y: axw asked for the interface
[23:58] <thumper> can you to duke it out
[23:58] <thumper> I don't particularly care one way or the other
[23:58] <thumper> but I'd like to start removing fslock asap
[23:58] <thumper> menn0: do you have an opinion on Acquirer interface vs. package function?


[00:01] <EventHorizon> removing backport still brings up the error series
[00:02] <valorie> what other PPAs do you have in there, EventHorizon?
[00:03] <EventHorizon> ubunty yakkety main, graphic driver, grub customizer - thats it under 'other'
[00:03] <valorie> hmmm
[00:03] <valorie> phantom PPA
[00:03] <EventHorizon> its probably main...
[00:04] <valorie> you don't want to remove the main repo
[00:04] <valorie> just the kubuntu-ppa
[00:05] <EventHorizon> OK thatnks for your help guys...  I'll have a think... Doesn't appear to be an easy fix at this stage.
[00:07] <valorie> sure it is
[00:07] <valorie> !repo
[00:07] <valorie> even if you have to edit a file, it's not hard to keep repos straight
[00:07]  * valorie is no guy either
[00:08] <EventHorizon> removing /kubuntu-ppa/ppa/ubuntu yakkety mian appears to have remove the error - any ideas why?
[00:08] <valorie> because it doesn't exist
[00:08] <valorie> as I said before
[00:09] <EventHorizon> sorry...  you probably did (have a toddler running around my legs - never a great time to pc probelm solve)
[00:09] <EventHorizon> Can i remove it from the listing easilty???
[00:10] <valorie> look at those links I gave to you
[00:10] <EventHorizon> will do... i'll save the log.  THANK YOU ALL!!!
[00:10] <valorie> easiest to just comment it out, but of course it can be removed as well
[00:10] <valorie> since it doesn't exist
[00:12] <EventHorizon> cheers. mate.
[09:09] <lordievader> Good morning
[09:12] <ilya> Hi :)
[09:21] <lordievader> Hey ilya
[09:21] <lordievader> How are you?
[09:27] <ilya> I am fine! Although can't say that about my Kubuntu installation...
[09:37] <lordievader> Why not?
[09:40] <ilya> Well, there are numerous really annoying bugs...  I thought they are caused by problems when upgrading to 16.10, but they seem to be common.
[09:42] <ilya> I thought about making a fresh install, but decided to install Kubuntu to a USB drive first, and now I see that many problems exist there as well.
[09:42] <ilya> Now think of installing openSUSE, Neon or Manjaro instead :(
[09:53] <lordievader> What kind of problems?
[10:35] <viewer|36621> Hello! I just installed kubuntu but there is a problem with nvidia driver... And I try to execute driver manager but nothing happen. Someone can help me?
[10:39] <Antony567> How to autostart few users?
[10:55] <ilya> lordievader, numerous. See this bug report, for example: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1633721
[10:56] <ilya> Also the network is not found from time to time, the only way to connect is rebooting.
[10:57] <ilya> See this report: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1434986
[10:58] <ilya> Considering the publication dates of those bug reports and message contents, I doubt they will ever be fixed.
[10:59] <lordievader> Hmm
[12:16] <user|70651> ciao
[12:27] <BluesKaj> Hiyas all
[17:01] <nikescomputers> Hello im a noob in kubuntu im have a error the following packages have unmet dependencies gwenview depends : libkf5kipi-bin 16.10
[18:11] <Lancelot> hey
[20:23] <yocs0000> what is the name of the root user on mysql in ubuntu?!
[20:28] <soee> yocs0000: root ?
[22:01] <Guest23911> Hello. I have a wierd bug. I want to install the system from USB and with default partitioning settings it gives me an error. Goes something like 'The partition /dev/sda1 assigned to /  starts at an offset of 3584 bytes form the minum alignment of this disk...'
[22:01] <Guest23911> and i can't get around that
[22:05] <DarinMiller> Guest23911: Open KDE partition manager and try resizing the partition.  Before resizing, click on the advanced button in the resize menu, and check the Align partition checkbox.
[22:08] <Guest23911> oh btw I tried other Ubuntu flavors too and they all have a problem with that, but just with this particular hdd
[22:13] <DarinMiller> Guest23911: If you don't need to keep the existing data you can just delete all existing partitions and start fresh.
[22:14] <Guest23911> there is nothing on there and just deleting all of it and letting the installer do the partitioning automatically makes it run into the error above
[22:19] <Guest23911> where can I send screenshots?
[22:23] <DarinMiller> Guest23911: If you can delete everything, use Patitition manager to create a new partition table and that should fix the problem.
[22:24] <Guest23911> still same error with that
[22:29] <DarinMiller> Guest23911: When you apply your changes in paritition manager does it return any errors?
[22:30] <DarinMiller> Guest23911: How big is your hard drive?
[22:30] <Guest23911> 1TB
[22:30] <Guest23911> and no
[22:31] <DarinMiller> Guest23911: Try manully creating 3 partitions.  I recommend creating 25 to 50G partition for root, a swap partitoin that is the same size as RAM and leave the rest for /home.
[22:32] <Guest23911> did that too. at the end of installing it gives me an error that says: "subprocess installed post-installation script returned error exit status 1"
[22:32] <DarinMiller> Guest23911: Use the manual option in the during install to manually assign "/" (root), set the swap type, and assign "/home".
[22:32] <DarinMiller> Kubuuntu 16.04?
[22:33] <Guest23911> yup
[22:34] <DarinMiller> Guest23911: I have had to fight this battle awhile back but I the steps above usually fix it.
[22:34] <DarinMiller> Guest23911: What type of BIOS?  UEFI?
[22:34] <Guest23911> BIOS
[22:34] <Guest23911> i'm installing on a pentium d
[22:35] <Guest23911> but the problem could be that i'm installing to an external hdd
[22:35] <Guest23911> and i have no way to get around that
[22:41] <DarinMiller> Guest23911: You may be fighting a BIOS issues that cannot handle 1TB HD's or partitions larger than a certain size (guessing here....).    Try creating 3 primary partitions and secondary parition to keep the partiton size under 500GB and see if that helps.  Also, it maybe your external HD HW does not support 1TB.  My older USB HD cases, choke on my 2.5" 1TB drive.
[22:42] <DarinMiller> Linux will mount the drive but incorrectly displays the partitions.
[22:42] <Guest23911> well i tried it on a different pc first so i think i can safely rule out bios issues
[22:43] <Guest23911> don't know about the other thing though. well i can use it as a normal external hdd for storage so i'm really not sure about that
[22:49] <DarinMiller> Guest23911:   Since you are install ing to the external HD, do you have a newer or different computer you could use to run the install?
[22:49] <Guest23911> i tried it on a 1yo laptop
[22:55] <DarinMiller> Guest23911: OK, then I am stumped.  Bring over to my house and I can throw  it in  my desktop and see if desktop HW makes a difference.
[22:56] <Guest23911> yeah nope :D
[22:56] <Guest23911> i could try it on my tower too but it'll probably fail the same way
[22:59] <Guest23911> i'll try to get the hdd out of the case and plug it in normally, and just putting it back in the case after install
[23:00] <DarinMiller> Guest23911: A couple years ago, I had use dd to re-write the boot sector as none of the std partition tools would touch the drive.  It worked but it was awhile go  so I don't remember the details.
[23:00] <Guest23911> ok wtf
[23:00] <Guest23911> i tried to make a new partiton table with fdisk
[23:01] <Guest23911> well it made a new table but still run into the same error while trying to install after that
[23:03] <Hailwood> Hey folks! Hopefully an easy question - I've recently setup my Kubuntu 16.10 system with three monitors (Integrated card HDMI, Dedicated HDMI, Dedicated DVI). It's working great except the monitor for the Dedicated HDMI doesn't have any "Desktop Environment". It's a strange one because I can drag windows onto it etc, I just can't right click the desktop and it has no wallpaper or panels.  I also end up with some wierd bar "ghosting" going on - http://i.imgur.com/rRDJBne.png See behind the IM icon?
[23:15] <Hailwood> Ok, ghosting fixed, just removed the overlayed bar.
[23:16] <Hailwood> Something that seems to be related is on the login screen the left and center screens are synced (if I type my password in one it appears in the other), but the right one seems to be acting on it's own.


[05:48] <maqtanim> Hi! Does anyone know how to approve a LoCo team?
[05:49] <coalwater> hi maqtanim , and no i don't im not really a member here, at least for now
[05:49] <coalwater> it's not in the wiki?
[05:50] <maqtanim> I didn't find it there
[05:50] <maqtanim> or may be I've missed that :(
[05:50] <coalwater> maqtanim, https://wiki.ubuntu.com/LoCoTeamHowto#Becoming%20an%20Approved%20Team
[05:51] <maqtanim> Thanks coalwater , I did not see that one... I am reading that right now
[05:52] <coalwater> np, good luck :)
[06:27] <YoBoY> good morning
[06:27] <coalwater> morning YoBoY
[07:04] <dholbach> good morning
[07:21] <coalwater> morning dholbach
[07:22] <dholbach> hi coalwater
[07:22] <coalwater> hi :)
[08:00] <BigWhale> Good morning.. for one last time ...
[08:00] <BigWhale> It's been nice knowing you people! *hugs*
[08:21] <YoBoY> ??? what's appen BigWhale ? :(
[08:30] <nigelb> BigWhale: Why the one last time?
[08:48] <BigWhale> Tomorrow is the end of the world? ;>
[08:49] <YoBoY> no, it's in 2012, not this year
[08:51] <BigWhale> no no.. the latest hype is May 21st 2011
[11:54] <daker> I got a spam (some kind of invitation) on the mailing list
[13:14] <mhall119> no no no, everybody knows the end of time is in 2038
[14:01] <highvoltage> mhall119: not if you use 64bit dates :)
[14:02] <coalwater> lol, i like that
[17:17] <daker> and here we go another spam :/
[17:17] <daker> LinkedIn invitation
[17:21] <YoBoY> daker: on which list do you receive that crap ?
[17:22] <daker> loco-contacts
[17:22] <daker> YoBoY, https://lists.ubuntu.com/archives/loco-contacts/2011-May/005329.html
[17:22] <daker> https://lists.ubuntu.com/archives/loco-contacts/2011-May/005330.html
[17:23] <YoBoY> ha ok, received too
[17:24] <YoBoY> strange mails...
[17:25] <YoBoY> but the first one was blocked on my spam box ^^"
[17:36] <daker> yes the first one was blocked but the second one not
[17:55] <YoBoY> the second seems a reply, it's why is not blocked
[17:56] <daker> yes
[17:58] <pleia2> loco directory people, did I do something wrong with flickr? "You don't have permission to view this pool"
[17:58] <pleia2> http://loco.ubuntu.com/teams/ubuntu-california
[17:58] <pleia2> it's all public
[17:59] <pleia2> (I can submit a bug, just not sure if I'm doing something wrong)
[18:03] <YoBoY> i can see the same message, can you give me the link to the flicker feed ?
[18:08] <pleia2> http://www.flickr.com/photos/ubuntu-us-ca
[18:09] <pleia2> oh, I put in the flickr name not the thing from idgettr
[18:09] <nigelb> pleia2: looking.
[18:09] <pleia2> it works now, sorry :)
[18:09] <pleia2> that's confusing though
[18:10] <YoBoY> flikr problem for sure
[18:11] <nigelb> pleia2: for future reference, we moved the web dev stuff to -website :)
[18:11] <pleia2> nigelb: oh, sorry :)
[18:13] <nigelb> pleia2: nah, we didn't do any formal announce.  We just decided to move our stuff there so as not to pollute here with web development stuff :)
[18:16] <YoBoY> nigelb: you already moved ? :O it was not just talking about it?
[18:16] <nigelb> YoBoY: we've taken all our discussions there instead of here.  We'll all still hang out here though.
[18:17] <YoBoY> yes but who will defend the french "not like the others" loco team ? :D
[18:18] <daker> pleia2, i don't see any message and i see 14 pictures
[18:19] <pleia2> daker: yes, I fixed it it
[18:19] <pleia2> -it
[18:19] <daker> ok
[18:26] <nigelb> YoBoY: hahah
[18:27] <YoBoY> what ? :)
[18:27] <YoBoY> hey I already make a proposition to improve all websites on this new chan :)
[18:28] <nigelb> YoBoY: "yes but who will defend the french "not like the others" loco team ? :D"
[18:56] <mhall119> pleia2: still need help?
[18:56] <pleia2> mhall119: nope, sorted
[18:56] <mhall119> awesome
[18:56] <pleia2> was just confused about what the flickr id was :)
[18:56] <pleia2> it's not your flickr login id, it's the idgettr id