/srv/irclogs.ubuntu.com/2015/08/26/#juju.txt

=== iceyec_ is now known as iceyec
claw_Not sure if this is the right place to ask, but hopefully it's a good start.  Is anyone able to help with problems I'm having with metadata services and shared_secret_keys not being passed around properly?  Or can point me somewhere that might be more appropriate to ask?07:52
=== anthonyf is now known as Guest39525
lukasaIf I use juju set keystone admin-password=<some password> once my OpenStack deployment is up, should I expect Horizon to automatically pick this change up?10:13
lukasaBecause it doesn't seem to10:13
WalexI am seeing in the Juju 'all-machines.log' several periods where there are lines like: "machine-0: message repeated 46502 times: [2015-08-25 09:49:53 WARNING juju.lease lease.go:301 A notification timed out after 1m0s.]" where should I start looking? That seems to be causing problems...10:56
josejcastro: hey, you submitting a talk for fossetcon?12:39
jcastrono I have devops days I am submitting to13:00
jcastrodo you want to submit this one?13:00
beisnergnuoy, can you review/land mongodb c-h sync re: Unsupported cloud: source option trusty-liberty/proposed?:  https://code.launchpad.net/~1chb1n/charms/trusty/mongodb/sync-fetch-helpers-liberty/+merge/26841313:06
gnuoybeisner, done13:09
beisnergnuoy, thanks.  fyi, pxc is in the same boat.  working on a mp now.13:09
stubIs anyone else seeing odd failures with juju-deployer? It seems to sometimes 'forget' do deploy a service, and then fails when it tries to add relations to the service it neglected to deploy.13:52
stubMaybe receiving out of date information when introspecting the environment?13:53
lazyPowerso lets say I got persnickety and turned off all of my EC2 vm's associated with my juju environment lastnight, when i powered them on this morning and fetched the new bootstrap node IP and updated my .jenv file with the proper bootstrap ip address, does anyone have suggestions as to why juju 1.24.4 cannot seems to get a response? the daemons are running on the state server13:53
lazyPowerjuju just seems to not be able to reach the node, and i'm suspect that the provider state file in s3 is the culprit....13:53
lazyPowerstub: is this a local charm declaration or a charmstore service?13:54
g3naroyou can telnet on port ?13:54
lazyPowerg3naro: let me try that, 1 sec13:54
stublazyPower: These are local charms13:54
g3naroif response, then maybe port is up but service is not responsive, try restart of agent on one box if possibe13:54
lazyPowerg3naro: yeah service is up but not responding, and there's a relevant security group rule13:55
lazyPoweri'm calling schenanigans13:55
g3narohmm13:55
lazyPowerstub: I'm not sure why that would be the case. does juju deploy the service just fine manually when you tell it to deploy local:series/foo?13:55
stublazyPower: Its buried three miles deep in the test suite, so hard to tell. I think it might be seeing a dying service that is taking its time to disappear. I might have to wait harder.13:57
lazyPowerstub: it would be nice if it had the option to force destroy services eh?13:58
lazyPowerforce destroy env, time-wait until service disappears - so we know its not an issue.13:58
stublazyPower: You can force destroy the machines, then you should always be able to destroy the service. But juju is async, so you still need to wait. I just didn't realize I needed to wait for that too.14:01
stub(assuming my guess is right)14:02
lazyPowerright14:03
lazyPoweri can see that, getting in a scenario where the service is stlil present in the env but has no units backing it, so you get this weird transient no unit but have a service situation14:03
josejcastro: yeah, I'm checking my schedule and looks like I can go. I think I'll submit a talk for then14:19
jcastroack.14:20
josejcastro: also, is it fine if I book now? later today the agent will be EOD (belgium based)14:20
jcastrosure, go for it!14:21
jcastrojose: seb has visa issues so he won't make it. *sadface*14:21
josejcastro: are you sure? he said he could get one fine... I'll double check in Spanish with him, maybe he meant something else14:21
joseI'll let you know how that goes14:21
jcastrono there's like a 20 day minimum14:21
jcastronext time we will book the hotel like 3 months in advance14:22
joseit's more than 20 days and afaik they give you the appointment for the next business day14:22
joseoh welp14:22
josebtw, if you need me to bring something from peru lmk14:22
g3narobro i would love 2 hot peru girls14:22
joseg3naro: don't think I can take those tu the summit :P14:23
g3narohehehe worth a shot14:23
Walexso I am getting on a master node of a Juju setup of a dozen nodes a few dozen thousands to a few millions warnings saying "WARNING juju.lease lease.go:301 A notification timed out after  1m0s.14:26
Walexper day... Sometimes thousands of those messages per second. And the Juju MongoDB db has perhaps relatedly grown to ~ 800 filles and 200GB. WHere to start looking?14:28
beisnerhi gnuoy, pxc ready for review/land.  cleaned up, ch-sync'd, passing.  https://code.launchpad.net/~1chb1n/charms/trusty/percona-cluster/liberty-prep/+merge/26921015:05
gnuoybeisner, done15:09
beisnergnuoy, ta!15:09
gnuoynp15:09
beisnergnuoy, coreycb - with today's mongodb and percona-cluster merges, that completes the Liberty uca ch-sync bit for all of the next charms in all of our tests.   Now we're completely clear to find other issues.  ;-)15:11
coreycbbeisner, nice, step by step..15:14
beisnercoreycb, yep.15:14
beisnerthanks again guys for the effort on all fronts.15:14
beisnerhi coreycb, in a spot where you can review/land this puppy?  https://code.launchpad.net/~ack/charms/trusty/keystone/pause-and-resume/+merge/26793115:18
coreycbbeisner, I took a quick glance but seeing as it's actions, james may want to take a scan15:19
beisnercoreycb, fyi it's parallel to what we've already landed in swift-storage (https://code.launchpad.net/~adam-collard/charms/trusty/swift-storage/add-pause-resume-actions/+merge/268233), so I think it's good to go.15:21
coreycbbeisner, ah, in that case...  I'll take a closer look15:22
coreycbbeisner, I'll look today, tied up in liberty packaging/mentoring atm15:22
beisnercoreycb, much appreciated15:22
mattywlazyPower, any update on https://github.com/juju/juju/issues/470?15:26
lazyPowerah i haven't looked at that in ages O_O15:28
lazyPowermattyw: I have no updates, but this looks to be something we just need to tune in the vagrant config?15:29
lazyPowerswap the port and adjust the python script thats setting up the GUI on boot15:29
lazyPoweraisrael: issue 470 linked above is in your fifedom if you have a moment to take a look and weigh in15:29
lazyPoweraisrael: and i swear i'm not passing the buck, just want your opinion as the current liason/maintainer of the vagrant workflow15:30
sparkiegeeklazyPower: btw /topic could do with an update ("Office Hours, here July 30'th")15:31
=== lazyPower changed the topic of #juju to: Welcome to Juju! || Juju Charmer Summit Sept. 18-19 US Washington DC - Ask us about details || Docs: http://juju.ubuntu.com/docs || FAQ: http://goo.gl/MsNu4I || Review Queue: http://review.juju.solutions || Unanswered Questions: http://goo.gl/dNj8CP
=== lazyPower changed the topic of #juju to: Welcome to Juju! || Juju Charmer Summit Sept. 18-19 US Washington DC - http://ubunt.eu/KorUSN || Docs: http://juju.ubuntu.com/docs || FAQ: http://goo.gl/MsNu4I || Review Queue: http://review.juju.solutions || Unanswered Questions: http://goo.gl/dNj8CP
lazyPowersparkiegeek: thanks :)15:33
aisraellazyPower: reading15:45
aisraellazyPower: I'm not sure if that error is still happening. Seeing if I can recreate it now.15:56
aisraelmattyw: Have you re-tested lately?15:56
mattywaisrael, I haven't - I'm on call reviewer today so I'm just going throught the issues on github and chasing things that might need to be chased16:00
aisraelmattyw: Gotcha. I'll follow up soon, thanks!16:01
aisraelmattyw: commented, but don't have perms to close. I'm unable to recreate. I believe this has been fixed within the vagrant image since the bug was opened.16:13
natefinch                      16:43
=== mrjazzcat is now known as mrjazzcat-afk
=== lifeless1 is now known as lifeless
=== natefinch is now known as natefinch-afk
ddellavcoreycb,  upgrade action mp complete and all tests pass: https://code.launchpad.net/~ddellav/charms/trusty/cinder/upgrade-action/+merge/26924721:05
coreycbddellav, cool, I'll take a look tomorrow21:05
ddellav:)21:06
joseniedbalski: ping, mind a quick PM?21:15
=== scuttlemonkey is now known as scuttle|afk
josealso, marcoceppi, http://review.juju.solutions/review/2196 needs clearing from the revq21:16
=== blr_ is now known as blr
=== scuttle|afk is now known as scuttlemonkey

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!