[12:29] <ejat> lazyPower: http://paste.ubuntu.com/11979459/
[21:43] <ejat> lazyPower: ?
[22:04] <lazyPower> ejat: looks like you've been stuck by this bug: https://bugs.launchpad.net/juju-core/+bug/1259675
[22:04] <mup> Bug #1259675: ERROR Get : 301 response missing Location header <juju-core:Opinion> <https://launchpad.net/bugs/1259675>
[22:15] <ejat> thanks lazyPower
[22:15] <ejat> reported 2014 ?
[22:16] <ejat> ........
[22:16] <lazyPower> it doesn't seem to be very common
[22:16] <lazyPower> If you dont need to recover the environment (as in nothing important is running in it) the easy fix is to remove the bucket that contains the state info file
[22:16] <ejat> i never had this problem before
[22:16] <lazyPower> and rebootstrap
[22:16] <lazyPower> yeah i dont know why its surfaced. its an older bug, i ran into it with a couple people in #juju back when i first started
[22:16] <lazyPower> but it hasn't come up again until now
[22:16] <ejat> remove the bucket in aws console ?
[22:16] <lazyPower> yeah
[22:17] <lazyPower> Load up S3 and find the juju bootstrap bucket
[22:17] <ejat> u want me to update the bugs ?
[22:17] <lazyPower> fwiw - we're removing that requirement in 1.25 - so the bucket related issue should go away.
[22:17] <lazyPower> that would be brilliant, that way we have a breadcrumb trail to follow should this come up again
[22:17] <ejat> owh ... so temp solution is to remove bucket manually ?
[22:18] <lazyPower> yeah :(
[22:18] <lazyPower> i haven't figured out how to fuly recover from it
[22:18] <lazyPower> since it never happened in my deployments i didn't have a busted env to poke at and find a proper fix
[22:19] <ejat> ok .. trying to remove it manually
[22:19] <ejat> but i've bump into another issue :)
[22:19] <ejat> http://paste.ubuntu.com/11982882/
[22:19]  * ejat contacting rackspace support .. waiting for their feedback as well 
[22:19] <ejat> its regard to tenant-name
[22:21] <lazyPower> ejat: aiui - we wont officially support rackspace until we land the new storageless provider code i referenced above
[22:21] <lazyPower> unless you use it in a manual provider space
[22:21] <ejat> lazyPower: sorry .. what is aiui
[22:21] <lazyPower> as i understand it
[22:22] <ejat> owh okie
[22:22] <lazyPower> if you could file a bug about that as well - https://bugs.launchpad.net/juju-core/+filebug
[22:22] <ejat> to bad for me for the short form :)
[22:22] <ejat> about the rackspace issue ?
[22:22] <lazyPower> That would get you a notification once its corrected,  I'll tag it and poke the core team about it
[22:22] <lazyPower> yes
[22:22] <ejat> ok ..
[22:28] <ejat> lazyPower: bug 1480616
[22:28] <mup> Bug #1480616: juju with RackSpace configuration <juju-core:New> <https://launchpad.net/bugs/1480616>
[22:28] <lazyPower> thanks ejat
[22:28] <ejat> most welcome
[22:28]  * ejat just wondering no one using juju with rackspace :) 
[22:28] <lazyPower> Sorry  I didn't have better news for you :-\ but we're certainly working on those issues.
[22:29] <ejat> no worries .. u help a lot at least i know its a bugs
[22:29]  * ejat just missed the juju core team , marco .. kapil .. james ... because no UDS anymore .. cant met them 
[22:30] <ejat> bcoz change to UOS :)
[22:30]  * ejat pokes marcoceppi
[22:31]  * ejat pokes jamespage
[22:34] <ejat> lazyPower: sorry to bother u again
[22:34] <ejat> http://paste.ubuntu.com/11982946/ <-- hpcloud
[22:37] <lazyPower> hmm, thats generic. are you able to ping the IP of the bootstrap node contained in your hpcloud .jenv file?
[22:44] <lazyPower> ejat: i've got to run for a bit, but i'll circle back when i get home to check on you
[22:44] <ejat> ok
[22:44] <ejat> lazyPower: back to amazon issue after removing S3
[22:44] <ejat> http://paste.ubuntu.com/11982991/
[22:44] <ejat> do i need to manually create in S3 ?
[22:45] <ejat> okie .. take ya time ... will wait for u when u get home .. no worries .. thanks
[23:35] <ejat> lazyPower: juju with azure :( http://paste.ubuntu.com/11983218/