This has been accepted into precise-backports.
** Changed in: precise-backports
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to txaws in Ubuntu.
https://bugs.launchpad.net/bugs/945176
Title:
This looks good, uploading based on feedback from SpamapS on IRC.
** Changed in: precise-backports
Status: Confirmed => In Progress
** Changed in: precise-backports
Assignee: (unassigned) => Micah Gersten (micahg)
--
You received this bug notification because you are a member of Ubu
build log of juju from precise building with backported txaws
** Attachment added: "buildlog-juju-precise-backported-txaws.txt"
https://bugs.launchpad.net/ubuntu/precise/+source/txaws/+bug/945176/+attachment/3250699/+files/buildlog-juju-precise-backported-txaws.txt
--
You received this bug n
Also tested backported aws-status, which is an indicator built on top of
txaws. Works fine in precise.
** Changed in: precise-backports
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to txaws in Ubuntu.
ht
Testing juju (only rdep of python-txaws) with backported txaws, works
perfectly:
Setting up juju (0.5+bzr531-0ubuntu1.2) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
(precise-amd64)root@clint-MacBookPro:/home/clint/pkg/txaws/backport# su - clint
(precise-
This is the output of the test program. Note that the backtrace about
NoneType is normal (coding error due to my ignorance of how to do things
perfectly in twisted).
$ python test-txaws-ipaddress.py ami-9666e9a6
i-e5269ad6
Mon Aug 6 16:32:33 2012: polling ec2...
Mon Aug 6 16:32:33 2012: polling
Attaching successful no-change source rebuild on precise of quantal
version.
** Attachment added: "txaws_0.2.3-1ubuntu1_amd64-20120806-1629.build"
https://bugs.launchpad.net/precise-backports/+bug/945176/+attachment/3250690/+files/txaws_0.2.3-1ubuntu1_amd64-20120806-1629.build
--
You receive
Also attaching some test code I wrote to show where ip_address will or
will not appear as a valid attribute depending on the version of txaws.
If the patch is cherry picked, the ipaddress shows up, but
terminateInstances raises an error because of the missing shutdownState.
** Attachment added: "t
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
** Changed in: txaws (Ubuntu Precise)
Milestone: ubuntu-12.04.1 => precise-updates
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to txaws in Ubuntu.
https://bugs.launchpad.net/bugs/945176
Title:
Support privateIpAddress and ipAddr
** Changed in: txaws (Ubuntu Precise)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to txaws in Ubuntu.
https://bugs.launchpad.net/bugs/945176
Title:
Support privateIpAddress and ipAddress
To manage noti
** Changed in: txaws (Ubuntu Precise)
Milestone: None => ubuntu-12.04.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to txaws in Ubuntu.
https://bugs.launchpad.net/bugs/945176
Title:
Support privateIpAddress and ipAddress
To man
Evaluating for SRU to precise since this is a huge missing piece of the
EC2 API
** Also affects: txaws (Ubuntu)
Importance: Undecided
Status: New
** Changed in: txaws (Ubuntu)
Status: New => Fix Released
** Also affects: txaws (Ubuntu Precise)
Importance: Undecided
Sta
13 matches
Mail list logo
