** Also affects: euca2ools
Importance: Undecided
Status: New
** Changed in: euca2ools
Assignee: (unassigned) = Mitch Garnaat (mitch-garnaat)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
** Also affects: euca2ools
Importance: Undecided
Status: New
** Changed in: euca2ools
Assignee: (unassigned) = Mitch Garnaat (mitch-garnaat)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It shouldn't fail as of revno 1257 as noted above :)
Did you try that revno?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/711534
Title:
euca-upload-bundle fails when
Definitely not that :)
This is fixed in the source but not released in package form yet.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/711534
Title:
euca-upload-bundle fails
It shouldn't fail as of revno 1257 as noted above :)
Did you try that revno?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711534
Title:
euca-upload-bundle fails when connecting to Eucalyptus and
Definitely not that :)
This is fixed in the source but not released in package form yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711534
Title:
euca-upload-bundle fails when connecting to
Marek, it means that the bucket (goldmann-test) needs to be created
first. The directory structure is part of the key.
Hope that helps.
neil
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
Marek, it means that the bucket (goldmann-test) needs to be created
first. The directory structure is part of the key.
Hope that helps.
neil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711534
Fixed in revno 1260.
** Branch linked: lp:eucalyptus
** Changed in: eucalyptus
Status: New = Fix Committed
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The command specified in the bug report doesn't work with AWS S3 unless
the user has actually created the bucket somehow. I just tested this.
For instance, if you use the option -b mybucket/abcd/efgh S3 will
correctly interpret this request (PUT to mybucket/abcd/efgh) as an empty
put to the
The command specified in the bug report doesn't work with AWS S3 unless
the user has actually created the bucket somehow. I just tested this.
For instance, if you use the option -b mybucket/abcd/efgh S3 will
correctly interpret this request (PUT to mybucket/abcd/efgh) as an empty
put to the
waltc, did you install eucalyptus-walrus and have you registered Walrus?
You will get that warning (Walrus URL is not configured) if you
download credentials before you have Walrus registered.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
waltc, did you install eucalyptus-walrus and have you registered Walrus?
You will get that warning (Walrus URL is not configured) if you
download credentials before you have Walrus registered.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This was fixed in 1195.1.151 (2.0.0-lp).
** Branch linked: lp:~eucalyptus-maintainers/eucalyptus/2.0.0-lp
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eucalyptus
Importance: Undecided = Medium
** Changed in: eucalyptus
Assignee:
This was fixed in 1195.1.151 (2.0.0-lp).
** Branch linked: lp:~eucalyptus-maintainers/eucalyptus/2.0.0-lp
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eucalyptus
Importance: Undecided = Medium
** Changed in: eucalyptus
Assignee:
Public bug reported:
Looks like this is a regression that did not make it into the 2.0 branch
(it works against the devel branch).
** Affects: eucalyptus
Importance: Medium
Status: Fix Committed
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
**
Fixed in 2.0.0-lp.
--
With versioning turned on, PUT object does not return version id in the header
https://bugs.launchpad.net/bugs/661565
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs
Public bug reported:
Looks like this is a regression that did not make it into the 2.0 branch
(it works against the devel branch).
** Affects: eucalyptus
Importance: Medium
Status: Fix Committed
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
**
Fixed in 2.0.0-lp.
--
With versioning turned on, PUT object does not return version id in the header
https://bugs.launchpad.net/bugs/661565
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: eucalyptus/trunk
Importance: Undecided
Status: New
** Also affects: eucalyptus/eucalyptus-devel
Importance: Undecided
Status: New
** Changed in: eucalyptus/1.5
Status: New = Won't Fix
** Changed in: eucalyptus/eucalyptus-devel
Status: New = Fix
** Changed in: eucalyptus
Status: Triaged = In Progress
** Changed in: eucalyptus
Status: In Progress = Confirmed
** Changed in: eucalyptus
Assignee: (unassigned) = Mitch Garnaat (mitch-garnaat)
--
euca2ools does not correctly specify port when $http_proxy is set
** Changed in: eucalyptus
Status: New = Confirmed
** Changed in: eucalyptus
Assignee: (unassigned) = Mitch Garnaat (mitch-garnaat)
--
euca2ools should include --region support
https://bugs.launchpad.net/bugs/485113
You received this bug notification because you are a member of
** Changed in: eucalyptus
Status: New = Invalid
** Also affects: euca2ools
Importance: Undecided
Status: New
** Changed in: euca2ools
Assignee: (unassigned) = Mitch Garnaat (mitch-garnaat)
--
euca2ools often output error messages to stdout
** Also affects: eucalyptus/trunk
Importance: Undecided
Status: New
** Also affects: eucalyptus/eucalyptus-devel
Importance: Undecided
Status: New
** Changed in: eucalyptus/1.5
Status: New = Won't Fix
** Changed in: eucalyptus/eucalyptus-devel
Status: New = Fix
** Changed in: eucalyptus
Status: New = Won't Fix
** Changed in: eucalyptus
Status: Won't Fix = Invalid
--
axis2c.log is full of spurious (and full of typos) errors
https://bugs.launchpad.net/bugs/456099
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: eucalyptus
Status: Triaged = In Progress
** Changed in: eucalyptus
Status: In Progress = Confirmed
** Changed in: eucalyptus
Assignee: (unassigned) = Mitch Garnaat (mitch-garnaat)
--
euca2ools does not correctly specify port when $http_proxy is set
** Changed in: eucalyptus
Status: New = Confirmed
** Changed in: eucalyptus
Assignee: (unassigned) = Mitch Garnaat (mitch-garnaat)
--
euca2ools should include --region support
https://bugs.launchpad.net/bugs/485113
You received this bug notification because you are a member of
** Changed in: eucalyptus
Assignee: (unassigned) = chris grzegorczyk (chris-grze)
--
euca-modify-image-attribute -l -a exits success on non-existant id
https://bugs.launchpad.net/bugs/546572
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: eucalyptus
Status: New = Invalid
** Also affects: euca2ools
Importance: Undecided
Status: New
** Changed in: euca2ools
Assignee: (unassigned) = Mitch Garnaat (mitch-garnaat)
--
euca2ools often output error messages to stdout
** Changed in: eucalyptus
Status: New = Invalid
--
After upgrade Lucid-Maverick, Eucalyptus database seems not to have been
upgraded
https://bugs.launchpad.net/bugs/646100
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus
** Changed in: eucalyptus
Status: New = Invalid
--
After upgrade Lucid-Maverick, all nodes need to be re-registered
https://bugs.launchpad.net/bugs/644759
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Changed in: eucalyptus
Status: New = Invalid
--
On upgrade from Lucid to Maverick CC entries in
/etc/eucalyptus/eucalyptus.local.conf are commented out
https://bugs.launchpad.net/bugs/644733
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: eucalyptus
Status: New = Incomplete
--
euca-* commands stopped responding
https://bugs.launchpad.net/bugs/639639
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing
** Changed in: eucalyptus
Status: New = Invalid
--
After upgrade Lucid-Maverick, Eucalyptus database seems not to have been
upgraded
https://bugs.launchpad.net/bugs/646100
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: eucalyptus
Status: New = Invalid
--
After upgrade Lucid-Maverick, all nodes need to be re-registered
https://bugs.launchpad.net/bugs/644759
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: eucalyptus
Status: New = Invalid
--
On upgrade from Lucid to Maverick CC entries in
/etc/eucalyptus/eucalyptus.local.conf are commented out
https://bugs.launchpad.net/bugs/644733
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: eucalyptus
Status: New = Incomplete
--
euca-* commands stopped responding
https://bugs.launchpad.net/bugs/639639
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eucalyptus
Status: New = Invalid
--
eucalyptus-common 2.0+bzr1241-0ubuntu4 not configured after package upgrade
https://bugs.launchpad.net/bugs/652815
You received this bug notification
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eucalyptus
Status: New = Invalid
--
eucalyptus-common 2.0+bzr1241-0ubuntu4 not configured after package upgrade
https://bugs.launchpad.net/bugs/652815
You received this bug notification
Fixed in revno 1240.
** Changed in: eucalyptus
Status: New = Fix Committed
** Branch linked: lp:~eucalyptus-maintainers/eucalyptus/2.0.0-lp
--
metadata service returns 500 error
https://bugs.launchpad.net/bugs/637659
You received this bug notification because you are a member of Ubuntu
Make sure you increase the disk space reserved for volumes (default is
50G) if you expect volume creation beyond that limit to succeed :)
Also, not sure I read the previous message correctly. There are fixes to
the CLC as well as the SC so you will need to upgrade and restart both.
--
[SRU]
Fixed in revno 1240.
** Changed in: eucalyptus
Status: New = Fix Committed
** Branch linked: lp:~eucalyptus-maintainers/eucalyptus/2.0.0-lp
--
metadata service returns 500 error
https://bugs.launchpad.net/bugs/637659
You received this bug notification because you are a member of Ubuntu
Sylvain, are you positive that you are running the right version? Did
you start from a clean state? Are there any other error messages on the
storage controller? Is lvdisplay, vgdisplay and pvdisplay added to the
white list of commands?
We have tested this several times on our end and I'm puzzled
Sylvain, are you positive that you are running the right version? Did
you start from a clean state? Are there any other error messages on the
storage controller? Is lvdisplay, vgdisplay and pvdisplay added to the
white list of commands?
We have tested this several times on our end and I'm puzzled
17:29:44 ERROR [SystemUtil:pool-10-thread-4]
com.eucalyptus.util.ExecutionException: ///usr/lib/eucalyptus/euca_rootwrap
losetup /dev/loop151 error: loop: can't get info on device /dev/loop151: No
such device or address
com.eucalyptus.util.ExecutionException: ///usr/lib/eucalyptus/euca_rootwrap
17:29:44 ERROR [SystemUtil:pool-10-thread-4]
com.eucalyptus.util.ExecutionException: ///usr/lib/eucalyptus/euca_rootwrap
losetup /dev/loop151 error: loop: can't get info on device /dev/loop151: No
such device or address
com.eucalyptus.util.ExecutionException: ///usr/lib/eucalyptus/euca_rootwrap
Make sure you start with a clean installation when you rerun the test.
Thanks!
--
eucalyptus create and delete volumes sometimes fail on lvm commands (POC + ENT
configs)
https://bugs.launchpad.net/bugs/590929
You received this bug notification because you are a member of Ubuntu
Server Team,
Make sure you start with a clean installation when you rerun the test.
Thanks!
--
eucalyptus create and delete volumes sometimes fail on lvm commands (POC + ENT
configs)
https://bugs.launchpad.net/bugs/590929
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've applied another fix (revno 1236, 1.6.2 branch) that makes cleanup
of volumes more robust (1235 solves part of the problem). This has been
tested on our end.
--
eucalyptus create and delete volumes sometimes fail on lvm commands (POC + ENT
configs)
https://bugs.launchpad.net/bugs/590929
You
I've applied another fix (revno 1236, 1.6.2 branch) that makes cleanup
of volumes more robust (1235 solves part of the problem). This has been
tested on our end.
--
eucalyptus create and delete volumes sometimes fail on lvm commands (POC + ENT
configs)
https://bugs.launchpad.net/bugs/590929
You
in: eucalyptus/1.6.2
Status: In Progress = Fix Committed
** Changed in: eucalyptus/1.6.2
Assignee: (unassigned) = Neil Soman (neilsoman)
--
eucalyptus create and delete volumes sometimes fail on lvm commands (POC + ENT
configs)
https://bugs.launchpad.net/bugs/590929
You received this bug
in: eucalyptus/1.6.2
Status: In Progress = Fix Committed
** Changed in: eucalyptus/1.6.2
Assignee: (unassigned) = Neil Soman (neilsoman)
--
eucalyptus create and delete volumes sometimes fail on lvm commands (POC + ENT
configs)
https://bugs.launchpad.net/bugs/590929
You received this bug
Also note that any transient failures in deletion are reported correctly
to the user now, i.e., a subsequent describe request will list any
volumes that could not be deleted for any underlying back end reason.
After this fix, the system should no longer be in an inconsistent state
where the
I have been unable to reproduce this issue against 2.0. Going to try
against 1.6.2 and report back.
@Dustin,
Volume: Error while communicating with Storage Controller:
CreateStorageVolume:Your proposed upload exceeds the maximum allowed
object size.
Web UI-configuration tab. Please increase the
Marking it invalid against the latest dev branch (2.0), but I will try
to reproduce it against 1.6.2.
** Changed in: eucalyptus
Status: New = Invalid
--
eucalyptus create and delete volumes sometimes fail on lvm commands
https://bugs.launchpad.net/bugs/590929
You received this bug
** Also affects: eucalyptus/eucalyptus-devel
Importance: Undecided
Status: New
--
cloud-debug.log reports errno=2 trying to execute 'bttrack'
https://bugs.launchpad.net/bugs/613535
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Against 1.6.2, I tried a test which involved creating and deleting 50
volumes in a tight loop, which passed successfully. With 100 volumes, I
was able to trigger a failure to clean up volumes. In addition, once the
max volume limit is reached and exceeded, occasionally, volumes are not
cleaned up
I have been unable to reproduce this issue against 2.0. Going to try
against 1.6.2 and report back.
@Dustin,
Volume: Error while communicating with Storage Controller:
CreateStorageVolume:Your proposed upload exceeds the maximum allowed
object size.
Web UI-configuration tab. Please increase the
Marking it invalid against the latest dev branch (2.0), but I will try
to reproduce it against 1.6.2.
** Changed in: eucalyptus
Status: New = Invalid
--
eucalyptus create and delete volumes sometimes fail on lvm commands
https://bugs.launchpad.net/bugs/590929
You received this bug
** Also affects: eucalyptus/eucalyptus-devel
Importance: Undecided
Status: New
--
cloud-debug.log reports errno=2 trying to execute 'bttrack'
https://bugs.launchpad.net/bugs/613535
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Against 1.6.2, I tried a test which involved creating and deleting 50
volumes in a tight loop, which passed successfully. With 100 volumes, I
was able to trigger a failure to clean up volumes. In addition, once the
max volume limit is reached and exceeded, occasionally, volumes are not
cleaned up
Public bug reported:
This is a server side issue. The fix is trivial.
** Affects: eucalyptus
Importance: Undecided
Status: Fix Committed
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
revno: 1226
fixes bug(s): https://launchpad.net/bugs/617032
committer: Neil n...@pall
branch nick: devel
timestamp: Thu 2010-08-12 13:42:58 -0700
message:
fixes LP: #617032
revno: 1227 [merge]
fixes bug(s): https://launchpad.net/bugs/611769
committer: Neil
branch nick: devel
timestamp: Thu 2010-08-12 18:11:39 -0700
message:
fixes LP: #611769
Public bug reported:
This is a server side issue. The fix is trivial.
** Affects: eucalyptus
Importance: Undecided
Status: Fix Committed
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
revno: 1226
fixes bug(s): https://launchpad.net/bugs/617032
committer: Neil n...@pall
branch nick: devel
timestamp: Thu 2010-08-12 13:42:58 -0700
message:
fixes LP: #617032
revno: 1227 [merge]
fixes bug(s): https://launchpad.net/bugs/611769
committer: Neil
branch nick: devel
timestamp: Thu 2010-08-12 18:11:39 -0700
message:
fixes LP: #611769
If users would like S3 bittorent API support, bittorent needs to be
installed. This has been the case since 1.6. bttrack is provided by
bittorent. We should probably do something to report this more, err,
nicely.
--
cloud-debug.log reports errno=2 trying to execute 'bttrack'
Revno 1219 makes this a bit clearer in the logs.
--
cloud-debug.log reports errno=2 trying to execute 'bttrack'
https://bugs.launchpad.net/bugs/613535
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
If users would like S3 bittorent API support, bittorent needs to be
installed. This has been the case since 1.6. bttrack is provided by
bittorent. We should probably do something to report this more, err,
nicely.
--
cloud-debug.log reports errno=2 trying to execute 'bttrack'
Revno 1219 makes this a bit clearer in the logs.
--
cloud-debug.log reports errno=2 trying to execute 'bttrack'
https://bugs.launchpad.net/bugs/613535
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: eucalyptus
Importance: Undecided
Status: New
** Changed in: eucalyptus
Assignee: (unassigned) = Neil Soman (neilsoman)
** Changed in: eucalyptus
Importance: Undecided = High
** Changed in: eucalyptus
Status: New = Fix Committed
--
EBS volume cannot
FYI, this does not affect xen users. Only kvm is affected.
--
EBS volume cannot be detached after i reboot a instance
https://bugs.launchpad.net/bugs/586542
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Also affects: eucalyptus
Importance: Undecided
Status: New
** Changed in: eucalyptus
Assignee: (unassigned) = Neil Soman (neilsoman)
** Changed in: eucalyptus
Importance: Undecided = High
** Changed in: eucalyptus
Status: New = Fix Committed
--
EBS volume cannot
FYI, this does not affect xen users. Only kvm is affected.
--
EBS volume cannot be detached after i reboot a instance
https://bugs.launchpad.net/bugs/586542
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Yes, I understand. I was replying to this part: As an added benefit,
performance should increase significantly. This is not necessarily
true, and in some cases, we have seen 10% performance degradation by
moving to virtio.
It will be a while until all distros move to libvirt 0.8.1. From an
Yes, I understand. I was replying to this part: As an added benefit,
performance should increase significantly. This is not necessarily
true, and in some cases, we have seen 10% performance degradation by
moving to virtio.
It will be a while until all distros move to libvirt 0.8.1. From an
Just as a warning, we have seen cases where enabling virtio for disks
actually degrades performance when compared to scsi for dynamically
attached disks. We will be enabling virtio for the next release, but it
important (from the upstream's point of view) that it be an option.
--
dynamic block
Just as a warning, we have seen cases where enabling virtio for disks
actually degrades performance when compared to scsi for dynamically
attached disks. We will be enabling virtio for the next release, but it
important (from the upstream's point of view) that it be an option.
--
dynamic block
This is a generic message that is printed out when attempting to list a
bucket that does not exist. Suppressing this warning will lead to
situations where the admin is trying to debug why a certain bucket is
not available and there is nothing in the logs that indicates failure.
The client tools do
I found at least 3 topics on the forum that reference this issue:
http://open.eucalyptus.com/search/node/NoSuchBucketException
http://open.eucalyptus.com/forum/why-did-error-occur
We apologize if this is not documented in the way you expect. Please
consider participating to help make the
Hi Alex, there is not enough information in your report to figure out
what is wrong with your installation. At the very minimum, we need
nc.log.
Please see open.eucalyptus.com/forum for help with this problem. The bug
tracker is only for filing bugs.
hope that helps
neil
** Changed in:
Hi Alex, there is not enough information in your report to figure out
what is wrong with your installation. At the very minimum, we need
nc.log.
Please see open.eucalyptus.com/forum for help with this problem. The bug
tracker is only for filing bugs.
hope that helps
neil
** Changed in:
There was another place where memory was being leaked. This was
happening after a register requests, so that over time, after a number
of register requests, Walrus would OOM. The issue was with the
interaction between the CLC and Walrus.
This is fixed in revno 1227.
--
walrus reports
There was another place where memory was being leaked. This was
happening after a register requests, so that over time, after a number
of register requests, Walrus would OOM. The issue was with the
interaction between the CLC and Walrus.
This is fixed in revno 1227.
--
walrus reports
revno: 1225
committer: Neil Soman
branch nick: 1.6.2
timestamp: Sat 2010-04-24 12:09:26 -0700
message:
fixes LP: #565101
** Changed in: eucalyptus
Importance: Undecided
revno: 1225
committer: Neil Soman
branch nick: 1.6.2
timestamp: Sat 2010-04-24 12:09:26 -0700
message:
fixes LP: #565101
** Changed in: eucalyptus
Importance: Undecided
Is this still an issue? Any updates?
How do we reproduce this on the upstream side?
thanks.
--
Rebundled uec instance boot fail
https://bugs.launchpad.net/bugs/551847
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to euca2ools in ubuntu.
Is this still an issue? Any updates?
How do we reproduce this on the upstream side?
thanks.
--
Rebundled uec instance boot fail
https://bugs.launchpad.net/bugs/551847
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Committed Chris' fix as revno 1215 to Eucalyptus.
** Changed in: eucalyptus
Status: In Progress = Fix Committed
** Branch linked: lp:eucalyptus
--
euca-describe-snapshots gives different output than ec2-describe-snapshots
https://bugs.launchpad.net/bugs/547059
You received this bug
Committed Chris' fix as revno 1215 to Eucalyptus.
** Changed in: eucalyptus
Status: In Progress = Fix Committed
** Branch linked: lp:eucalyptus
--
euca-describe-snapshots gives different output than ec2-describe-snapshots
https://bugs.launchpad.net/bugs/547059
You received this bug
I object to fixing this in the client library. If this is a bug in the
service, it should be fixed in the service. So what happens when it is
fixed in Eucalyptus? It is removed from boto? You could argue that it
doesn't have to be, since boto would continue to work regardless of
whether an int or
I object to fixing this in the client library. If this is a bug in the
service, it should be fixed in the service. So what happens when it is
fixed in Eucalyptus? It is removed from boto? You could argue that it
doesn't have to be, since boto would continue to work regardless of
whether an int or
Definitely a regression due to 530296 and not 531076
--
euca-describe-images img lists all images when querying against ec2
https://bugs.launchpad.net/bugs/541468
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to euca2ools in ubuntu.
--
Reintroducing the workaround fixes this problem. The list from EC2
includes all images even if an image id is specified.
--
euca-describe-images img lists all images when querying against ec2
https://bugs.launchpad.net/bugs/541468
You received this bug notification because you are a member of
Fixed in revno 268.
Describe images asks for a list of images as before (instead of asking
for all images). It will then double check the list against the list
specified by the user and display only the intersection, just in case
the service sends back all images.
** Changed in: eucalyptus
Yeah, looks like I can get boto to return the correct image is by
setting owners and executable_by to None. If executable_by is set to
['self'], nothing is returned, which does not make a lot of sense.
Good luck getting to the bottom of this. Frankly, this is beyond the
scope of euca2ools
Definitely a regression due to 530296 and not 531076
--
euca-describe-images img lists all images when querying against ec2
https://bugs.launchpad.net/bugs/541468
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Reintroducing the workaround fixes this problem. The list from EC2
includes all images even if an image id is specified.
--
euca-describe-images img lists all images when querying against ec2
https://bugs.launchpad.net/bugs/541468
You received this bug notification because you are a member of
Fixed in revno 268.
Describe images asks for a list of images as before (instead of asking
for all images). It will then double check the list against the list
specified by the user and display only the intersection, just in case
the service sends back all images.
** Changed in: eucalyptus
1 - 100 of 374 matches
Mail list logo
