[13:45] <marcoceppi> I'm back
[14:47] <amithkk> marcoceppi: You have a question to answer
[14:48] <amithkk> Oh, you answered <3
[17:03] <ihashacks> Ok, so after a few weeks of working with Juju + LXC I've decided to step it up to EC2 testing.
[17:04] <ihashacks> I did my bootstrap but just get tons of "ERROR Invalid SSH key" in "status" or "debug-log"
[17:04] <ihashacks> All I've found on web searches are a lot of "wait longer," "destroy-environment and try again," and "make sure you have the ssh-keygen setup"
[17:06] <ihashacks> I know I have my ssh keys setup and working properly, "destroy-environment and try again" seems silly and I don't know how much "wait longer" I need.
[17:12] <ihashacks> ...except that now the local .ssh/ is empty O_o
[17:14] <marcoceppi> ihashacks: destroy the environment, re-run ssh-keygen, bootstrap, try again?
[17:16] <ihashacks> ...trying
[17:16] <ihashacks> I *know* those damn ssh keys were there at first because you get an error about keys not found if you try to run juju w/o them
[19:49] <SpamapS> ihashacks: are you getting errors because you don't have a *known* key for the instances?
[19:49] <SpamapS> ihashacks: thats something different entirely
[20:18] <lamont> the laptop actually made it home this morning... I'll fetch it from the car shortly
[20:19] <SpamapS> ihashacks: it would help if you paste binned the errors
[20:19] <lamont> bah. ECHAN
[22:54] <ihashacks> SpamapS: series of events 1) run "juju bootstrap" 2) edit environments.yaml 3) run "juju bootstrap" (receive error about missing SSH keys) 4) run ssh-keygen 5) this time "juju bootstrap" completes, node in ec2 running 6) "juju status" received "ERROR Invalid SSH key"
[22:55] <ihashacks> 7) destroy-environment and start over
[22:55] <ihashacks> ^^^ worked
[22:55] <SpamapS> ihashacks: interesting
[22:55] <SpamapS> ihashacks: I'd be interested to see that ssh key error
[22:57] <ihashacks> I guess juju warned about SSH key, bootstrapped anyways, then when I tried to run "status" it obviously didn't have a key in the running image for me to authenticate with
[22:58] <SpamapS> *ahhh*
[22:58] <ihashacks> and the error received was the generic "you don't have ssh keys" message when you run juju before ssh-keygen
[23:00] <ihashacks> I did notice an interesting "bug" perhaps in ec2-zone constraints. I set "ec2-zone=a" for a mysql server, the node shows in "juju status" but nothing was ever loaded in ec2
[23:00] <ihashacks> My dashboard in AWS only shows zones b,c,d for me which is why I think it didn't actually "work" in ec2
[23:00] <ihashacks> I haven't started with a fresh environment since that issue earlier to confirm that I can repeat the issue.
[23:00] <marcoceppi> ihashacks: those aren't the same zones I don't think
[23:01] <marcoceppi> nevermind, I'm confusing regions with zones
[23:01] <ihashacks> ec2-zone=b and c had the desired result
[23:12] <SpamapS> ihashacks: Sounds like the provider should use the describeAvailabilityZones call to validate your constraints
[23:13] <SpamapS> ihashacks: there's a bug to have constraints be pre-checked at some point.
[23:13] <SpamapS> ihashacks: most likely the provisioning agent was spewing errors once per minute
[23:21] <ihashacks> This one: https://bugs.launchpad.net/juju/+bug/984640
[23:21] <_mup_> Bug #984640: Unsatisfied constraints are not reported back to the user <juju:Confirmed> < https://launchpad.net/bugs/984640 >
[23:21] <ihashacks> ?
[23:21] <_mup_> Bug #984640: Unsatisfied constraints are not reported back to the user <juju:Confirmed> < https://launchpad.net/bugs/984640 >