Cannot bootstrap instances in ec2

John Arbash Meinel john at arbash-meinel.com
Tue Apr 2 07:34:48 UTC 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-04-02 10:28, David Cheney wrote:
> This was the changeset that broke deployments.
> 
> http://bazaar.launchpad.net/~juju/juju-core/trunk/revision/1078
> 
> I have raised
> 
> https://bugs.launchpad.net/juju-core/+bug/1163122
> 
> and
> 
> https://canonical.leankit.com/Boards/View/103148069/104639172
> 

Are you using --upload-tools?

I tried just reverting -r1078, but that ends up with a bunch of
conflicts, because code that was changed s/EntityName/Tag/ was
refactored. So it isn't trivial to just revert it.

Grepping the code, I see a lot of places where we didn't quite expunge
the phrase "entity name" even though it is now called Tag. However,

"state entity name not found in configuration"

Doesn't exist in the code base, but "state entity tag not found in
configuration" does.

Which makes me think you are running a new juju client which is
setting the "Tag" value somewhere in the DB, but an old juju agent,
which is looking for "entity name".

I expect the error you are getting is from ~line 111 in
environs/agent/agent.go but that should now be erroring based on
'state entity tag'.

Sounds like 1.9.13-dev isn't compatible with 1.9.12. (Not too unexpected.)

Now if you did use --upload-tools, then I think we have something more
serious.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFaihgACgkQJdeBCYSNAAPQnACgjqx7RG8xpt3fi2UV1ZsOMBfB
uwIAoKZBXnSWJZJkU2v9b0UF+s/L3DXX
=rI1d
-----END PGP SIGNATURE-----



More information about the Juju-dev mailing list