This is still an issue in maaverick.
** Also affects: mysql-dfsg-5.1 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Importance: Undecided = Medium
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Status: New = Triaged
** Changed in:
Public bug reported:
Running one instance every ~60-seconds; after a while we started getting
FinishedVerify: Cannot mark address as
allocating[unallocated.false-allocated.true] when it is assigned.true:
[Address id=5 name=10.55.55.104 cluster=UEC-TEST1 userId=nobody
instanceId=available
This bug is present now because eucalyptus-nc added a dependency on
grub-pc. I believe that this caused grub-pc to get installed earlier in
the installation process, before some other things were properly set up.
The reason for the dependency on grub-pc is that eucalyptus-nc is
creating a boot
** Tags added: lucid
--
package clamav-freshclam 0.95.3+dfsg-1ubuntu0.09.10 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 100
https://bugs.launchpad.net/bugs/530555
You received this bug notification because you are a member of Ubuntu
Server
Thierry, does this fail 100% of the time ?
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
--
Instance does not start
https://bugs.launchpad.net/bugs/613514
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus
Jamin,
I suspect this is related to apparmour profile for libvirt. Do you see
messages in dmesg after attempting this ?
** Also affects: virt-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Low
** Changed in: libvirt
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
--
Cannot mark address as allocating[unallocated.false-allocated.true] when it is
assigned.true:
https://bugs.launchpad.net/bugs/613832
You received this bug notification because you are a member of Ubuntu
Server Team, which
Could you please include what version of the package you're running?
** Changed in: puppet (Ubuntu)
Importance: Undecided = Medium
** Changed in: puppet (Ubuntu)
Status: New = Triaged
--
undefined method `closed?' for nil:NilClass when signing certificate
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Medium
** Changed in: qemu-kvm (Ubuntu)
Status: New = Triaged
--
qem/kvm misinterprets LVM volume geometry
https://bugs.launchpad.net/bugs/613619
You received this bug notification because you are a member of Ubuntu
Server Team,
Sorry if this is the wrong place to post such a message, but I'm
experiencing this issue on a production host and it's a significant
issue. I have to reboot my machine regularly, and this bug is causing
boot to take well over 30 minutes.
Is there a workaround I can use until the next stable
Adding upstream: Is this a new pre-req?
** Also affects: eucalyptus
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
Dooitze,
Thanks for the reply on reproducibility, but could you please post squid.conf
as Clint asked?
--
squid crashed with SIGFPE in main()
https://bugs.launchpad.net/bugs/608177
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct
On that specific i386 setup, yes. I tried 4 instances and they all failed.
I set up an amd64 one and it was working correctly. Might be an i386-specific
issue, or a setup-specific issue.
** Summary changed:
- Instance does not start
+ Mavreick i386 UEC: Instance does not start
** Summary
Here are some discussions where I found problems mentioned that seem to
be the same or closely related problem:
http://www.howtoforge.com/forums/archive/index.php/t-30329.html
http://ubuntuforums.org/showthread.php?t=1425421
I am not sure yet what exactly the reason is, but I experienced similar
After testing the changes in the squid upstart configuration introduced by
commit 51, package squid (2.7.STABLE9-2ubuntu1) maverick, it seems that the max
filedescriptors ulimit is still not applied.
Setting the ulimit using the script section (instead of setting it in the
pre-start script
** Tags added: maverick
--
[10.10 - Alpha 3 (candidate)] Prompts misleading grub dialogs during UEC Node
installation.
https://bugs.launchpad.net/bugs/613463
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Had it again on the stress test. Once it happens, it keeps on happening.
Upstream seems to have some fixes for IP address allocation, so we will
wait for them.
--
Cannot mark address as allocating[unallocated.false-allocated.true] when it is
assigned.true:
https://bugs.launchpad.net/bugs/613832
aaronbauman,
This bug is believed to be fix-released in lucid (lucid-updates).
I think its probably best if you open a new bug and describe the issue
you're having.
Please open the bug with 'ubuntu-bug eucalyptus' on the cluster controller
that way related debug information will be
This bug was fixed in the package openldap - 2.4.23-0ubuntu1
---
openldap (2.4.23-0ubuntu1) maverick; urgency=low
* New release, features include:
+ Fixed libldap to return server's error code (ITS#6569)
+ Fixed libldap memleaks (ITS#6568)
+ Fixed liblutil off-by-one
This bug was fixed in the package openldap - 2.4.23-0ubuntu1
---
openldap (2.4.23-0ubuntu1) maverick; urgency=low
* New release, features include:
+ Fixed libldap to return server's error code (ITS#6569)
+ Fixed libldap memleaks (ITS#6568)
+ Fixed liblutil off-by-one
This bug was fixed in the package openldap - 2.4.23-0ubuntu1
---
openldap (2.4.23-0ubuntu1) maverick; urgency=low
* New release, features include:
+ Fixed libldap to return server's error code (ITS#6569)
+ Fixed libldap memleaks (ITS#6568)
+ Fixed liblutil off-by-one
Rebooted the server and now I'm no longer getting the Could not
determine original disk information: Disk '/dev/group/volume' does not
exist. error. However it fails to actually perform the cloning with the
following:
Traceback (most recent call last):
File
We got this in our long term test too. It looked like an addressing
issue that we are aware of. Chris has an fix to be committed. I will
update once this is confirmed.
--
Cannot mark address as allocating[unallocated.false-allocated.true] when it is
assigned.true:
Public bug reported:
Binary package hint: euca2ools
$ euca-terminate-instances i-abcdefg echo good || echo bad:$?
good
$ xc2 terminate-instances i-abcdefg echo good || echo bad:$?
Client.InvalidInstanceID.Malformed: Invalid id: i-abcdefg
bad:1
If you pass euca-terminate-instances a bogus
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/53116499/Dependencies.txt
--
euca-terminate-instances returns success on bogus input
https://bugs.launchpad.net/bugs/613940
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Description changed:
Binary package hint: euca2ools
$ euca-terminate-instances i-abcdefg echo good || echo bad:$?
good
- $ xc2 terminate-instances i-abcdefg echo good || echo bad:$?
+ $ ec2-terminate-instances i-abcdefg echo good || echo bad:$?
Client.InvalidInstanceID.Malformed:
@Scott, setting a low importance and wishlist status - as it doesn't
seem to be a major issue.. Is there something i've missed? If so,
please feel free to escalate the importance.
** Changed in: euca2ools (Ubuntu)
Status: New = Confirmed
** Changed in: euca2ools (Ubuntu)
Importance:
Confirming:
ubu...@cempedak:~/uec-testing-scripts$ euca-terminate-instances i-xaxa; echo $?
0
ubu...@cempedak:~/uec-testing-scripts$ euca-terminate-instances xaxa; echo $?
Invalid instance id
1
ubu...@cempedak:~/uec-testing-scripts$
** Changed in: euca2ools (Ubuntu)
Importance: Wishlist =
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Triaged
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
does not support cloning vm storage on lvm backend
https://bugs.launchpad.net/bugs/613549
You received this bug notification because
Jamin, can you add the following to /etc/apparmor.d/usr.sbin.libvirtd:
capability fsetid,
Then do:
$ sudo apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.libvirtd
and report back if it resolves the issue for you.
** Changed in: libvirt (Ubuntu)
Status: Triaged = Incomplete
--
does
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.
--
Thanks, Neil.
So we need to add a depends bittorrent|bittornado for the Walrus
package.
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
** Changed in: eucalyptus (Ubuntu)
Status: New = Triaged
--
cloud-debug.log reports errno=2 trying to execute 'bttrack'
Public bug reported:
On Ubuntu 10.04, I was recently unable to start two virtual machine.
Both produced the same error. The error reported by virt-manager was
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 588, in run_domain
vm.startup()
File
Made the requested apparmor change, checked the dmesg output before
attempting to clone the VM, found the following new entry:
[90351.748748] type=1505 audit(1281033561.731:23):
operation=profile_replace pid=7783 name=/usr/sbin/libvirtd
Looks good so far.
First attempt to clone the VM and set
Heh. Sorry Dave, it seems both of us got here at about the same time.
Setting back as WishList.
** Changed in: euca2ools (Ubuntu)
Importance: Medium = Wishlist
--
euca-terminate-instances returns success on bogus input
https://bugs.launchpad.net/bugs/613940
You received this bug notification
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: libvirt (Ubuntu)
Status: New = Triaged
--
Uninformative libvirt error message when a virtual disk source is unavailable
https://bugs.launchpad.net/bugs/613969
You received this bug notification because you
Pete,
What problem were you seeing exactly?
The upstart jobs cloud-* do not explicitly list 'cloud-config' as a 'start
on' requirement. That is by design. cloud-init starts on:
(mounted MOUNTPOINT=/ and net-device-up IFACE=eth0)
That set of events actually blocks any other upstart
Public bug reported:
Binary package hint: openvpn
After boot the smbd and nmbd services are not bound to the tap interface
created by openvpn. I think this is because openvpn is started after samba,
because after a
# service nmbd restart
# service smbd restart
everything works fine.
I saw the
We have the same problem in our business environment at the place I work
at. I think this is an upstart problem as how can samba connect to an
existing cups server when it hasn't started yet. Samba needs to depend
on cups.
--
CUPS starts after SAMBA; printers are not available (convert cups to
Jamin, were there any other apparmor denied messages in kern.log after
you made the profile changes and tried again?
--
does not support cloning vm storage on lvm backend
https://bugs.launchpad.net/bugs/613549
You received this bug notification because you are a member of Ubuntu
Server Team,
No, nothing.
Here is the full kern.log since the reload:
Aug 5 12:39:21 kvm-host kernel: [90351.748748] type=1505
audit(1281033561.731:23): operation=profile_replace pid=7783
name=/usr/sbin/libvirtd
Aug 5 12:46:07 kvm-host kernel: [90757.988390] lo: Disabled Privacy Extensions
Aug 5
** Package changed: grub (Ubuntu) = grub2 (Ubuntu)
--
[10.10 - Alpha 3 (candidate)] Prompts misleading grub dialogs during UEC Node
installation.
https://bugs.launchpad.net/bugs/613463
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: eucalyptus
Assignee: (unassigned) = chris grzegorczyk (chris-grze)
** Changed in: eucalyptus
Status: New = In Progress
--
eucalyptus-cloud: cloud fails to start on separate install
https://bugs.launchpad.net/bugs/613033
You received this bug notification because you
** Changed in: eucalyptus
Assignee: (unassigned) = chris grzegorczyk (chris-grze)
--
inconsistent output euca_conf and euca-describe-availability-zones
https://bugs.launchpad.net/bugs/610259
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Could you verify this is still happening with the latest commits? I
guess one of my fixes solves the problem.
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
This bug was fixed in the package apparmor - 2.5.1~pre1393-0ubuntu1
---
apparmor (2.5.1~pre1393-0ubuntu1) maverick; urgency=low
* Update to upstream bzr revision 1393 from lp:apparmor/2.5.
* add dbus-session abstraction (LP: #566207)
* require owner in user-tmp abstraction
** Branch linked: lp:ubuntu/apparmor
--
mysql configuration should be adjusted to help prevent against chained attacks
against LAMP stack
https://bugs.launchpad.net/bugs/578922
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: nagios
Status: New = Fix Released
--
should recognize that exit code 126 means plugin is not executable
https://bugs.launchpad.net/bugs/471468
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios3 in ubuntu.
--
+1 for importance.
--
libvirt-bin hypervisor does not support virConnectNumOfInterfaces / unable to
create domain with virt-manager using network bridge
https://bugs.launchpad.net/bugs/520386
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Sorry about that Scott yes I had an old source for the cloud-init
upstart script your correct about the mount point.
The issue I was seeing is that the system was trying to query user data
prior to the system loading it from the meta data service. So by
waiting for cloud-init to load the
51 matches
Mail list logo
