landscape-client should send extra cloud data to the server to prevent collisions when searching for the cloud that it's on
Bug #343942 reported by
Christopher Armstrong
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
landscape-client (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: landscape-client
Right now it's conceivable that two instances in different EC2 clouds (like on different Eucalyptus deployments) would have the same instance key. We currently try to find the cloud that an instance is in by iterating all the clouds in an account and getting all its instance IDs. This means there are potential mismatches during registration. The client should send extra data, from the EC2 metadata that is available to it, to the server.
To post a comment you must log in.
This bug was fixed in the package landscape-client - 1.0.28- 0ubuntu1. 9.04.0
--------------- 0ubuntu1. 9.04.0) jaunty; urgency=low
landscape-client (1.0.28-
* Fix minor packaging issues in last release (LP: #343954) ation data (LP: #343942) and allow the EC2 user data to specify
- Version number in landscape.VERSION is now correct
- Fixed package version number to maintain convention
* The following changes are in the 1.0.28 release:
- Invalidate package cache when server UUID changes (LP: #339948)
- Improve the "cloud mode" introduced in 1.0.26 to send more
disambigu
the exchange and ping URLs (LP: #343947)
- Allow importing of initial configurations (along with public SSL
certificates) when running landscape-config (LP: #341705)
- Support a non-root mode which allows running the client without the
management functionality (LP: #82159)
- Automatic cloud registration when there's no user-data to specify an OTP
now works (LP: #344323)
-- Christopher Armstrong <email address hidden> Thu, 19 Mar 2009 09:52:03 -0400