© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On initial investigation of the given patch, it seemed that this problem would be fairly easy to solve with a cherry picked patch.
But, this is not so. ipAddress and privateIpAddress were not present in the default version of the EC2 API that txaws supported in the release shipped in precise (EC2 API version 2008-12-01).
Passing an EC2 query object which setts the API version at 2009-11-30, when the attributes were added, does work, but then causes failures in other areas of txaws which had to be updated for the newer WSDL, such as changing 'shutdownState' to 'currentState' in terminate_
This is a red flag for me, and I think this has to be either be changed to a micro release update with a ton of regression testing, or the new version must be pushed to precise-backports, and anything (like juju) that wants to take advantage of the new attributes needs to be careful to only use them if they are available.
Marking the Precise SRU as Won't Fix, and opening a task against precise-backports, as that is the more conservative approach. We may decide to go forward with a micro release update if we can come up with a good testing plan, but it doesn't seem likely.