revno: 1208
fixes bug(s): https://launchpad.net/bugs/532682
committer: Neil
branch nick: 1.6.2
timestamp: Mon 2010-03-08 14:39:06 -0800
message:
fixes LP: #532682
** Change
Hello,
The Eucalyptus upstream will default to key injection if the metadata
service is not available. On the UEC, key injection is turned off. The
images on the Eucalyptus website will try the metadata service, but if
you are running vanilla Eucalyptus, it will attempt to do key injection
as well
I have added a note at the bottom of the Eucalyptus documentation
http://open.eucalyptus.com/wiki/EucalyptusUserImageCreatorGuide_v1.6
** Changed in: eucalyptus
Status: New => Fix Committed
--
Metadata service not documented
https://bugs.launchpad.net/bugs/531571
You received this bug no
There should a "Delete User" link next to the user. You cannot delete
the admin. If a user is marked as an administrator, you need to remove
admin privileges first (Edit) and then the Delete User link will appear.
--
Cannot remove UEC/Eucalyptus users from webUI
https://bugs.launchpad.net/bugs/53
** Changed in: euca2ools
Status: New => Fix Committed
--
the version specified in euca2ools setup.py needs to be updated
https://bugs.launchpad.net/bugs/522396
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
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 a
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 noti
Definitely a regression due to 530296 and not 531076
--
euca-describe-images 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 list
Reintroducing the workaround fixes this problem. The list from EC2
includes all images even if an image id is specified.
--
euca-describe-images 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
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 function
This was fixed a while ago. The fix should be in the current 1.6.2
branch.
revno: 1068.1.28
committer: Neil
timestamp: Wed 2009-12-23 12:04:40 -0800
message:
fixes to get inline data.
** Changed in: eucalyptus
Status: Confirmed => Fix Committed
** Branch linked: lp
I can't confirm this against euca2ools upstream. Is there a sample image
that can be used stand alone with euca2ools in order to verify this?
** Changed in: euca2ools (Ubuntu)
Status: Confirmed => Incomplete
--
euca-bundle-image returns Odd-length string error
https://bugs.launchpad.net/b
revno: 218
committer: Neil
branch nick: euca2ools-1.0
timestamp: Mon 2009-10-05 15:43:40 -0700
message:
fixes #444105
** Changed in: eucalyptus
Status: New => Fix Com
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
If the volume id specified is incorrect euca-attach-volume displays a error but
proceeds to send the attach request to the server
https://bugs.launchpad.net/bugs/444097
You received this bug notification because
revno: 210
committer: Neil
branch nick: euca2ools-1.0
timestamp: Thu 2009-09-10 15:28:21 -0700
message:
fixes #427367
** Changed in: euca2ools (Ubuntu)
Status: New =
revno: 219
committer: Neil
branch nick: euca2ools-1.0
timestamp: Tue 2009-10-06 10:40:25 -0700
message:
fixes #444747
** Changed in: eucalyptus
Status: New => Fix Com
My bad, linked it to the wrong package in Ubuntu. Thanks Thierry.
--
euca-describe-volumes does not show the zone in which the volume resides
https://bugs.launchpad.net/bugs/444105
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
"The underlying problem is not the error reporting itself. There is (as
I pointed out earlier) a formatting problem that causes the client tools
to not display the error message in many cases."
I agree that there is a formatting issue. However, failed requests should not
send back a HTTP 200. It
Just to clarify, I opened the bug because the HTTP code returned was not
correct. There are two issues,
1. HTTP error code reported when registration fails.
2. Formatting of the error response.
They could both be addressed here, but the intention was not to start a
"metabug" that covers all erro
Still doesn't quite work as expected. Reopening.
** Changed in: eucalyptus
Status: Fix Committed => In Progress
--
In SYSTEM mode + multicluster, instances do not run on multiple clusters
https://bugs.launchpad.net/bugs/444908
You received this bug notification because you are a member of
Confirmed! thanks.
--
In SYSTEM mode + multicluster, instances do not run on multiple clusters
https://bugs.launchpad.net/bugs/444908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
Public bug reported:
--list-scs does not show the SC and the SC seems to have been
deregistered. However, it still receives heartbeat messages.
** Affects: eucalyptus
Importance: Low
Status: New
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Sum
revno: 1067
committer: root
branch nick: 1.6
timestamp: Sat 2009-11-07 12:30:31 -0800
message:
fixes #46
** Changed in: eucalyptus
Status: Confirmed => Fix Commit
Thierry, please see,
http://bazaar.launchpad.net/~eucalyptus-
maintainers/eucalyptus/1.6/revision/1067
(Apparently our launchpad sync script was failing. I have pushed the
latest manually).
--
Query string authentication does not work in some cases
https://bugs.launchpad.net/bugs/46
You rec
Please see https://bugs.launchpad.net/eucalyptus/+bug/450044
thanks.
--
Re bundled karmic image fails to boot
https://bugs.launchpad.net/bugs/479621
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
http://open.eucalyptus.com/wiki/EucalyptusUserImageCreatorGuide_v1.6
These should also be under the Extras tab in the UI.
--
Non-ubuntu Eucalyptus images won't work on UEC by default - no key injection
https://bugs.launchpad.net/bugs/457860
You received this bug notification because you are a me
I've linked it against the Karmic package. Upstream eucalyptus does not
have the "--discover-nodes" option and seems to be a UEC issue.
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
karmic cloud install fails at autodiscovery: wants both worlds (eucalyptus/r
Nick, that is correct. #450044 relates to the creation of some necessary
mount points for ubuntu images (/var/run, /var/lock).
There were a few issues with euca-bundle-vol. They have been fixed in
revnos 207, 208 and 221.
thanks.
--
euca-bundle-vol creates unuseable image?
https://bugs.launchpa
revno: 942
committer: Neil
branch nick: 1.6
timestamp: Mon 2009-10-26 09:36:30 -0700
message:
fixes #461156
** Changed in: eucalyptus
Status: New => Fix Committed
**
Turns out it is an issue with euca2ools and not eucalyptus. reverting.
revno: 943
committer: Neil
branch nick: 1.6
timestamp: Mon 2009-10-26 10:52:44 -0700
message:
reverting invalid fix in revno 942 (was not a bug).
-
revno: 222
committer: Neil
branch nick: euca2ools-1.0
timestamp: Mon 2009-10-26 11:00:47 -0700
message:
fixes #461301
** Changed in: eucalyptus
Status: New => Fix Com
See #461301
--
User data is not base64 decoded before being presented to the instance
https://bugs.launchpad.net/bugs/461156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
revno: 944
committer: Neil
branch nick: 1.6
timestamp: Mon 2009-10-26 13:04:33 -0700
message:
fixes #461394
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
I am unable to reproduce this problem.
euca-run-instances -k mykey --kernel eki-0212156F --ramdisk eri-604B16B8
emi-97BE1397 -z mycluster2 --user-data " << FOO >" --addressing private
RESERVATION r-405607B1 admin admin-default
INSTANCEi-45F30812 emi-97BE13970.0.0.0 0.
This issue seems similar to what we ran into on the upstream side which
revnos 931 and 933 fixed.
I can attempt to reproduce it from source against the latest upstream.
--
maximum 61 "running" instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notificati
Paul,
are these overprovisioned nodes? Or are those 384 real cores?
It looks like the front end is timing out while processing requests
because the nodes may not be responding fast enough.
What about disk? Can you walk us through your hardware config?
thanks
neil
--
maximum 61 "running" insta
Nope, hyperthreading should be fine.
I strongly suspect that addresses per subnet in eucalyptus.conf is either set
to 64 (that will give you 61 instances max and is consistent with your
behavior) or you increased the value but didn't restart the CC (it need to
"cleanrestart").
Can you post y
Scott, sorry I don't understand what you are saying.
You said "I'm also unable to reproduce Markus's problems with --user-
data ' << FOO >' and a patched euca2ools."
But you are still running into the "User authentication failed" issue?
I cannot reproduce this against the upsteam (current euca2o
Yep, I confirm that it is a bug against eucalyptus (not euca2ools). I
was using an older version of euca2ools that did double encoding of the
user data.
thanks.
** Changed in: eucalyptus
Status: Invalid => Confirmed
** Changed in: eucalyptus
Importance: Undecided => High
** Summary ch
** Changed in: eucalyptus
Status: New => Fix Committed
--
euca-describe-availability-zones verbose doesn't report the types of instances
available
https://bugs.launchpad.net/bugs/434036
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
revno: 899
committer: Neil
branch nick: 1.6
timestamp: Sun 2009-09-27 19:13:58 -0700
message:
fixes #430226
** Changed in: eucalyptus
Status: Confirmed => Fix Committ
I've re-targeted to 1.6
If you are using the 1.6 development and have existing users that you
care about, credentials will not work. Hopefully, this is a non issue
since folks are probably not using the 1.6 development branch in
production. If you want your existing users to work, you need to logi
revno: 221
committer: Neil
branch nick: euca2ools-1.0
timestamp: Mon 2009-10-12 20:05:41 -0700
message:
fixes #450044
** Changed in: eucalyptus
Status: New => Fix Co
I tried the following (revno 931 of eucalyptus and revno 221 of
euca2ools):
$euca-bundle-image -i /disk1//images/vmlinuz-2.6.28-11-generic -d iii -r
i386
$euca-upload-bundle -b test-image -m
iii/vmlinuz-2.6.28-11-generic.manifest.xml
$euca-register test-image/vmlinuz-2.6.28-11-generic.manifest.x
s/test-kkk/test-image/ (made a mistake in copy pasting).
--
euca-describe-images reports all UEC images as x86_64
https://bugs.launchpad.net/bugs/451358
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Looks like Thierry already marked it invalid so my comment is
superfluous :)
--
euca-describe-images reports all UEC images as x86_64
https://bugs.launchpad.net/bugs/451358
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This is a regression (caused by a slight typo).
revno: 932
committer: Neil
branch nick: 1.6
timestamp: Wed 2009-10-14 17:46:47 -0700
message:
fixes #451795
** Changed in:
I am unable to reproduce this problem. I am using Eucalyptus revno 931
and Euca2ools revno 221.
Perhaps something went wrong in the packaging?
$ euca-authorize default -P tcp -p 22 -s 0.0.0.0/0
GROUP default
PERMISSION default ALLOWS tcp 22 22 FROMCIDR
0.0.0.0/0
$ e
Please check the wire. I'd be interested in what the cloud is
actually responding with (ngrep -d -Wbyline port 8773) on the
front end.
It is likely something to do with packaging. I have never seen it with
the source install.
--
euca-authorize default failing
https://bugs.launchpad.net/bugs/452
I have linked this against the package. I can't reproduce it against a
source install.
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
ec2-describe-instances not working for non-admin credentials
https://bugs.launchpad.net/bugs/453177
You received this bug not
Nick,
do you have a server side exception/stack trace?
Are there other exceptions?
Something is definitely not right with the package.
thanks.
--
euca-authorize default failing
https://bugs.launchpad.net/bugs/452556
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
This causes the "volumes" dir to be created as root.
** Affects: eucalyptus
Importance: High
Status: New
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eucalyptus
Importance: Undecided => High
** Also affects
revno: 868
committer: Neil
branch nick: 1.6
timestamp: Thu 2009-09-24 16:32:40 -0700
message:
fixes #436276
** Changed in: eucalyptus
Status: New => Fix Committed
--
It has to do with migrating snapshots created with version 1.5 to 1.6.
If you create a snapshot in 1.5 and upgrade to 1.6 (not clean install),
your old snapshots may not be available (in multi component/multi
cluster mode). There is a fix for the migration in the head, but part of
the process requi
This was a problem with SYSTEM mode (UEC default is supposed to be
MANAGED_NOVLAN if I'm not mistaken so this shouldn't affect that). I
believe this was fixed but I need to confirm that against the upstream
(I will update this bug when I do).
--
SYSTEM mode, clc does not send runinstances.
https:
The current status for this is that the Storage Controller reports this
as an EntityTooLargeException (which is better than the cryptic error
that it used to), but the front end reports this as,
com.eucalyptus.util.EucalyptusCloudException: Error communicating with
Storage Controller: CreateStorag
Uhh, in revno 893, not 593 :)
--
SC registration through web UI fails
https://bugs.launchpad.net/bugs/436313
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
This should already be in Karmic.
revno: 769
committer: decker
branch nick: 1.6
timestamp: Wed 2009-09-16 12:44:41 -0700
message:
fix escape path on runtime exceptions in snapshot describe
--
Loïc Minier, the patch to the Makefile has been applied upstream. Please
see
https://bugs.launchpad.net/eucalyptus/+bug/436950
Thank you.
--
[MIR] euca2ools
https://bugs.launchpad.net/bugs/434697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
MANAGED and MANAGED_NOVLAN work fine with revno 894.
SYSTEM mode shows the following behavior now.
The NC keeps getting run instance over and over.
cc.log
[Fri Sep 25 20:18:30 2009][019078][EUCADEBUG ] RunInstances(): called
[Fri Sep 25 20:18:30 2009][019078][EUCADEBUG ] refresh_resources(): ca
Revno 897 fixes this.
** Changed in: eucalyptus
Status: New => Fix Committed
--
SYSTEM mode, instances do not run
https://bugs.launchpad.net/bugs/430957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Every other (sometimes third) time, euca/ec2 describe volumes/snapshots
will "hang."
** Affects: eucalyptus
Importance: Undecided
Status: New
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Branch linked: lp:eucalyptus/1.6
*
revno: 764
committer: Neil
branch nick: 1.6
timestamp: Wed 2009-09-16 10:47:56 -0700
message:
fixes #430888
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
revno: 767
committer: Neil
branch nick: 1.6
timestamp: Wed 2009-09-16 11:51:22 -0700
message:
fixes #430922
** Branch linked: lp:eucalyptus/1.6
** Also affects: eucalyptus (
Public bug reported:
Multicluster (CLC/CC/SC Walrus/NC).
Resources are allocated, run instances not sent to the CC.
12:16:08 WARN ClusterNodeState | BEFORE ALLOCATE
12:16:08 WARN ClusterNodeState |
[VmTypeAvailability{type=VmType{name='m1.small', cpu=1,
This has been fixed in the upstream.
Please see https://launchpad.net/bugs/423465
thanks
--
euca.p12 owned by root
https://bugs.launchpad.net/bugs/423465
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
Public bug reported:
Attach does not correctly enforce this.
** Affects: eucalyptus
Importance: Undecided
Status: New
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Branch linked: lp:eucalyptus/1.6
** Also affects: eucalyptus (Ubuntu)
Import
revno: 789
committer: Neil
branch nick: 1.6
timestamp: Fri 2009-09-18 19:14:12 -0700
message:
fixes #432823
** Changed in: eucalyptus
Status: New => Fix Committed
-
This bug may cause public IP addresses to be associated with an
incorrect private address in MANAGED mode (especially in with multiple
clusters). This results in instances not being reachable.
** Changed in: eucalyptus
Importance: High => Critical
** Branch linked: lp:eucalyptus/1.6
** Also a
You can already set this via the MAX_CORES value in eucalyptus.conf on
individual nodes. It is unclear whether using a blanket value across all
nodes via the front end config is a good idea. We provide a finer level
control at the individual node level and I don't think this will be
changing for Ka
revno: 904
committer: Neil
branch nick: 1.6
timestamp: Fri 2009-10-02 10:47:47 -0700
message:
fixes #440744
** Changed in: eucalyptus
Status: New => Fix Committed
**
revno: 907
committer: Neil
branch nick: 1.6
timestamp: Fri 2009-10-02 12:08:08 -0700
message:
fixes #440817
** Changed in: eucalyptus
Status: New => Fix Committed
*
This is actually fixed in revno 908 (I forgot to add some necessary
files).
--
External command failure not handled correctly in some cases
https://bugs.launchpad.net/bugs/440744
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
revno: 1109
committer: Neil
branch nick: 1.6.2
timestamp: Fri 2009-12-18 17:14:05 -0800
message:
fixes LP: #498379
** Changed in: eucalyptus
Status: New => Fix Commi
revno: 1069
committer: root
branch nick: 1.6
timestamp: Fri 2009-11-13 09:13:45 -0800
message:
fixes #482249
** Changed in: eucalyptus
Status: New => Fix Committed
*
This fixes euca-bundle-vol and euca-bundle-image
--
euca2ools: euca-bundle-vol strips leading zero (0) from user id
https://bugs.launchpad.net/bugs/479823
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
revno: 231
committer: Neil
branch nick: euca2ools-1.0
timestamp: Fri 2009-11-13 10:02:43 -0800
message:
fixes #479823
** Changed in: eucalyptus
Status: Confirmed => F
Kendall, can you try "/dev/sdb" instead of "sdb" with euca-attach-volume
and report back?
thanks
neil
--
can't access SC volumes in a UEC instance
https://bugs.launchpad.net/bugs/452185
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** 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 becaus
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
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 buck
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
T
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.
h
** 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.
https://bugs.launchpad.net/bu
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: (unass
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 a
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 Euca
** 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.
--
ubu
** 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 l
** 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 subscribe
** 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
ubuntu-bugs@lists.ubuntu
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
** Cha
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
ubuntu-bugs@lists.ub
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 t
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 notifi
** 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 Ubuntu.
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 p
** 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 => Fi
** 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,
101 - 200 of 221 matches
Mail list logo
