/srv/irclogs.ubuntu.com/2015/05/06/#juju.txt

wgrantUsing juju-core 1.23.2 with the local provider on a vivid host with trusty containers, I'm not seeing config-changed fire.00:17
wgrantdebug-hooks never shows anything, despite no errors being visible in juju status.00:18
wgrantmachine-0: 2015-05-06 00:18:04 ERROR juju.worker runner.go:219 exited "machiner": cannot set machine addresses of machine 0: cannot set machineaddresses for machine 0: state changing too quickly; try again soon00:18
wgrantis filling my logs, but that's about the only interesting thing.00:18
lazyPower_wgrant: meaning it just skips? or you only get the install hook executed - and the rest of the hook queue is silently dropped?00:20
wgrantlazyPower_: I assume the install hook fired, as my services started. But even after a container reboot I still get nothing showing up in debug-hooks after I change config on any of my services.00:21
lazyPower_wgrant: install wouldnt necessarily equate to started - that means it thinks it reached the start hook. :|00:21
lazyPower_but, no config-changed after updating config is troubling00:21
lazyPower_are you certain there's nothing attached to a unit blocking hook context? eg: debug-hooks on a unit in a dependent container?00:22
wgrantlazyPower_: Well, I know install or config-changed fired at some point, as code that's only run in those cases has run at least once.00:22
wgrantEr, install or upgrade-charm, rather.00:23
lazyPower_right, i'm thinking what else could block a config-changed event00:27
lazyPower_but if no service is in error, no subordinates attached that are quietly in error, and no debug-hooks action on the unit... it seems like you've uncovered a bug :(00:27
=== kadams54-away is now known as kadams54
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
bdxHows it going everyone?03:38
bdxCan anyone give a few examples for possible values for the flat-network-providers config03:39
bdxfor quantum-gateway?03:39
thumperbdx: https://jujucharms.com/quantum-gateway/trusty/16 says "Space-delimited list of Neutron flat network providers."03:49
thumperbdx: I'm not sure what an individual Neutron flat network provider looks like03:50
thumperbut a wild stab in the dark would ip addresses03:50
lazyPower_thumper: you and I need to learn more about our big buddy openstack.03:51
thumperlazyPower_: almost certainly03:51
thumperlazyPower_: I'll put it up there with paxos and raft03:51
thumper:)03:51
lazyPower_I kinda sorta understand raft03:51
lazyPower_paxos however - pfffffffffffffffffft03:51
* thumper goes back to implementing 'juju system login'03:51
lazyPower_aint nobody got time for that03:51
bdxthumper: Thanks05:21
bdxDoes anyone know where a good example of deploying a dvr stack using juju might be located at?05:22
=== urulama_ is now known as urulama
=== stub` is now known as stub
lazyPower_bdx: are you referring to like deploying mythbuntu? (dvr = digital video recorder?)10:44
lazyPower_gsamfira: o/10:51
bdxlazyPower: no....openstack with dvr11:24
lazyPower_bdx: ah, looking into neutron stuff. i had to google it11:27
lazyPower_sorry :( i'm not going to be much help in this effort.11:27
lazyPower_hazmat: ping12:16
hazmatlazyPower_: pong13:31
lazyPower_hazmat: I found a solution to my problem during the break :)13:31
hazmatlazyPower_: cool13:32
jcastrolazyPower_, https://plus.google.com/hangouts/_/hoaevent/AP36tYfpg6vIOgpBcl3zoASu8vfjOaJViFvk6yT4g7z7CfU8B6QnCw?authuser=0&hl=en13:47
mgz_lazyPower_: when you have a mo, can you give some feedback on what output you actually want in the error cases for bug 1444861?14:03
mupBug #1444861: Juju 1.23-beta4 introduces ssh key bug when used w/ DHX <dhx> <ssh> <juju-core:Triaged> <juju-core 1.24:In Progress by hduran-8> <https://launchpad.net/bugs/1444861>14:03
mgz_perrito666 has a branch up, and it's pretty simple to make the output less vile at the same time14:03
mgz_(I'm thinking duplicate notices should just give fingerprint not whole line, and maybe we want to be more careful about what we call invalid?)14:04
lazyPower_mgz_: thanks for the follow up - I think thats a fine solution - i've also referred cory_fu the author of DHX to this error for his feedback if any.15:15
mgz_lazyPower_: ta15:16
=== urulama is now known as urulama__
=== wolsen_ is now known as wolsen
ennobleAnyone know if it's possible to get the juju action id from within the action environment?16:54
aisraelennoble: Yes, it should be there. I can check the key16:55
aisraelcharmers: This MP needs you: https://code.launchpad.net/~hatch/charms/precise/ghost/trunk/+merge/25516816:55
ennobleaisrael: I can't seem to find it in any environment variables, action-get, ...16:56
aisraelennoble: JUJU_ACTION_UUID16:57
ennoble- id: e23d3f13-15d6-4b82-8af5-1e151537892a   status: pending unit: test/016:57
ennobleaisrael: interesting, I don't see that environment variable in my action environment. I'm running 1.23.2-trusty-amd64 There is a JUJU_CONTEXT_ID and a JUJU_ENV_UUID=16:58
aisraelWhen you say 'action environment', are you testing this from machine you're running juju from, or inside an action when it's being executed (the action context)16:59
ennobleaisrael: inside the action when it's being executed. So I'm running juju debug-hooks <unit name>  and then running juju action do ... on another terminal. the action environment starts in debug-hooks tmux session and I'm looking at the environment variables17:00
hatchaisrael: hey that was merged17:00
hatchohh nm17:01
hatchit was reviewed but never merged :)17:01
aisraelhatch: Yeah, oops!17:01
hatchYEAH! get on it :P17:01
tvansteenburghaisrael, hatch: i'll merge it now17:01
hatch:) thanks tvansteenburgh17:01
hatchthat reminds me I should get back working on that17:02
hatchI'm torn on how to do backups though...17:02
hatchand upgrades17:02
aisraelennoble: action's can't be caught via juju debug-hooks, afaik. It's something we've asked to put on the roadmap for actions 2.017:03
ennobleaisrael: Are you sure? it's happening for me17:05
ennobleaisrael: the JUJU_HOOK_NAME is set to the action name and the parameters I passed to the action are available via action-get, so I'm fairly certain it's working17:06
aisraelennoble: confirming17:07
jw4aisrael, ennoble  yeah, I discovered recently that debug-hooks works with actions17:07
aisraeljw4: Excellent. Do we know if it's 100% working, i.e., the issue ennoble is seeing?17:08
aisraelsounds like he's getting a hook context env rather than the action's context17:08
jw4aisrael: no, it's accidentally working so I can easily imagine issues like ennoble is reporting17:08
jw4we can file a bug and get that fixed17:09
aisraelcharmers: This one needs some attention. I just +1'd it, based on the testing I did pre-Malta to fix an amulet bug (since released): https://bugs.launchpad.net/charms/+bug/136683417:12
mupBug #1366834: [New charm] Ubuntu repository cache for cloud partners <Juju Charms Collection:Fix Committed> <https://launchpad.net/bugs/1366834>17:12
aisraeljw4: Will you file, or would you like me to do it?17:17
ennobleaisrael: sorry I dropped off; is the JUJU_ACTION_ID available in a newer version of juju?17:21
aisraelennoble: The action working in the debug-hook is kind of accidental, and doesn't appear to be working the same as your running action would see it.17:22
ennobleaisrael: ok, so if I don't use the debug-hooks I should see the JUJU_ACTION_ID variable?17:23
aisraelennoble: correct. We'll get a bug filed for that so the behavior works as expected in a future release17:24
ennobleaisrael: thx! one more actions question: are the actions guaranteed to execute in the order that they were submitted by a single user? I found a discussion about this about 6 months ago on the mailing list and it looks like the conclusion was they should.17:25
aisraelennoble: Yes, they work like charm hooks in that they're queued and run in the order submitted17:26
ennobleaisrael: and charm hooks are ordered with actions as well? e.g. juju set ... juju action ... juju set ... juju action would respect that order?17:27
rick_h_https://wiki.ubuntu.com/MOTU/GettingStarted17:27
aisraelennoble: I believe it should, yes.17:27
rick_h_whoops, wrong channel ignore me17:27
ennobleaisrael: thx again17:28
jw4aisrael: sorry, OTP17:32
aisraelstub: you around?17:44
lazyPower_hatch: i lied, ping.17:47
lazyPower_er17:47
lazyPower_hazmat: i lied, re:ping.17:47
hatchwhat17:47
ennobleaisrael: I don't think JUJU_ACTION_ID is being set, even outside of the debug-hooks. i just logged all the environment variables and it's not there17:48
hatchoh :)17:48
hazmatlazyPower_: what's up?17:48
lazyPower_hazmat: any chance we can co-maintain the pypi project for juju-deployer?17:48
hazmatlazyPower_: sure17:48
hazmatlazyPower_: what's your pypi id?17:48
lazyPower_tvansteenburgh :D17:49
lazyPower_hehe, hang on, lemme fish that up17:49
lazyPower_pretty sure its lazypower - but i need to double check17:49
tvansteenburghyeah add me too17:49
hazmatlazyPower_: :-) that works.. i'll have to do it when i get home. don't have my credentials on my current computer17:49
aisraelennoble: it should be JUJU_ACTION_UUID17:52
ennobleaisrael: maybe I'm doing something wrong, but I'm not seeing it17:54
aisraelennoble: Can you pastebin what you're seeing? I'll get an environment w/actions spun up shortly and verify17:55
jw4aisrael: just got off the phone, but I'm out for a bit now.. if you'd like to file the bug that would be great.  Thanks!17:58
aisraeljw4: you got it17:59
lazyPower_duuuuude18:07
lazyPower_testing windows charms? use pester! https://github.com/pester/Pester18:07
lazyPower_#TIL18:07
rick_h_lazyPower_: ah yea cloudbase showed that off in nuremberg18:08
lazyPower_i just learned about this, i'm really impressed at the level of tooling they've written around charming for windows18:10
lazyPower_ahhh they didnt write pester, they just consumed it with great success.18:42
lazyPower_nifty all the same18:42
jcastrooffice hours here: https://plus.google.com/hangouts/_/hoaevent/AP36tYeqRbxEExDyG6Q6yjS24zxmhYScseYHDXq0S7Z59CrheB_ahg?authuser=0&hl=en18:48
jcastrooffice hours here: https://plus.google.com/hangouts/_/hoaevent/AP36tYeqRbxEExDyG6Q6yjS24zxmhYScseYHDXq0S7Z59CrheB_ahg?authuser=0&hl=en18:55
jcastrofor those of you on the other side of the netsplit18:55
jcastrowe'll be taking questions here and in #ubuntu-uos-cloud19:00
hazmatlazyPower_: added tvan for it, i don't see a pypi user for you19:39
lazyPower_bueno, i'll bug tim for gating :)19:40
lazyPower_thanks hazmat19:40
hazmatrick_h_: is there anyone on your team you want to have pypi uploads for deployer ?19:40
rick_h_hazmat: francesco and/or brad would be cool, but if we've got the others with access I'm happy to work through them19:40
hazmatrick_h_: added frankban19:41
rick_h_hazmat: ty19:41
ennobleaisrael: are you still around? here is the environment that I see http://pastebin.com/CdsuN7Sd I printed it from a python action so it's a dict (os.environ)22:02
ennobleaisrael: I see in the code where it's supposed to have JUJU_ACTION_(NAME|UUID|TAG) but it doesn't appear to be happening in my environment22:16
aisraelennoble: what version of juju are you running?22:17
ennobleaisrael: 1.23.222:19
aisraelennoble: Huh. Definitely a little strange. What's the command line you're invoking the action with?22:20
ennobleaisrael: juju action do test/0 bench22:21
aisraelennoble: here's what my env looks like: http://pastebin.ubuntu.com/11000481/22:30
aisraelennoble: Did you upgrade an environment from a previous version of juju?22:31
ennobleaisrael: possibly. I certainly was using 1.22 previously but I'm fairly certain I destroyed it and started over, however I'll do that now just in case22:34
aisraelennoble: if you run a juju status, you could see if the unit agents are on the newer version of juju22:35
aisraelThe only difference I see is the provider. I'm using local, but you're on maas. I wouldn't think that would make a difference, though.22:35
ennobleaisrael: yes, the agent version is 1.22,122:40
aisraelennoble: Ahh, that would probably do it. Either a fresh environment, or `juju upgrade-juju --upload-tools` should take care of it22:50
ennobleaisrael: thanks for all your help and sorry about the wild goose chase22:50
aisraelennoble: No worries! I'm glad we figured it out.22:50
aisraelennoble: Also, you should also see the JUJU_ACTION_ variables when you run debug-hooks22:57
aisraeljw4: fwiw, I am able to use debug-hooks against actions and everything appears to work.22:59
jw4aisrael: nice, thanks for verifying and letting me know too23:03
ennobleis there a floating point type that works with actions?23:30
aisrael`float` should work, I think23:33
ennobleaisrael: it seems like 1.23 is much more strict on action types.. int doesn't work but integer seems to, however float doesn't: invalid action "bench": float is not a valid type23:45
lazyPower_i thought actions only supported the same var types we have implemented for config - int, bool, and string23:56

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