** Branch linked: lp:~ubuntu-core-dev/eucalyptus/ubuntu
--
Walrus, SC and CC registrations hardcode 'localhost'
https://bugs.launchpad.net/bugs/437058
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
I've made some progress, and autoregistration is now succeeding for me.
I had to ditch the localhost registrations, and use a real IP address.
I pulled that functionality into a single place, that can be sourced by
each upstart file.
As of 1am, this is working for me.
I'm uploading now, and
This bug was fixed in the package eucalyptus - 1.6~bzr854-0ubuntu13
---
eucalyptus (1.6~bzr854-0ubuntu13) karmic; urgency=low
* eucalyptus-common.eucalyptus.upstart: the -L option was in the wrong
place, breaking the console.log logging, LP: #439161
*
This bug was fixed in the package eucalyptus - 1.6~bzr854-0ubuntu13
---
eucalyptus (1.6~bzr854-0ubuntu13) karmic; urgency=low
* eucalyptus-common.eucalyptus.upstart: the -L option was in the wrong
place, breaking the console.log logging, LP: #439161
*
This bug was fixed in the package eucalyptus - 1.6~bzr854-0ubuntu13
---
eucalyptus (1.6~bzr854-0ubuntu13) karmic; urgency=low
* eucalyptus-common.eucalyptus.upstart: the -L option was in the wrong
place, breaking the console.log logging, LP: #439161
*
Public bug reported:
Eucalyptus as of 1.6~bzr854-0ubuntu13 autoregisters components. However
those registered components are not put in use by the cloud webservice
until it is restarted.
So after installation you need to run:
$ sudo stop eucalyptus
$ sudo start eucalyptus
before making use of
to 20090930.
** Affects: eucalyptus (Ubuntu)
Importance: High
Status: New
** Affects: eucalyptus (Ubuntu Karmic)
Importance: High
Status: New
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = High
** Changed in: eucalyptus (Ubuntu)
Milestone: None = ubuntu
Public bug reported:
Binary package hint: postfix
n/a
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script returned error exit status 75
Package: postfix 2.5.5-1.1
SourcePackage: postfix
Title: package postfix 2.5.5-1.1 failed to
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32745024/Dependencies.txt
** Attachment added: DpkgTerminalLog.txt
http://launchpadlibrarian.net/32745025/DpkgTerminalLog.txt
--
package postfix 2.5.5-1.1 failed to install/upgrade: subprocess
post-installation script
** Changed in: samba4 (Ubuntu)
Status: Triaged = Fix Released
** Changed in: samba4 (Ubuntu)
Assignee: (unassigned) = Jelmer Vernooij (jelmer)
--
samba4 should 'Conflicts:' with samba-tools
https://bugs.launchpad.net/bugs/278864
You received this bug notification because you are a
** Visibility changed to: Public
--
virsh crashed with SIGSEGV in virDomainCreate()
https://bugs.launchpad.net/bugs/438395
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
Public bug reported:
Registering a walrus on localhost fails with an internal error message:
$ sudo euca_conf --register-walrus localhost
Adding WALRUS host localhost
Internal Error.
ERROR: failed to register Walrus, please log in to the admin interface and
check cloud status.
This was done
** Attachment added: eucalyptus-logs.tar.bz2
http://launchpadlibrarian.net/32747582/eucalyptus-logs.tar.bz2
--
Internal error registering local walrus
https://bugs.launchpad.net/bugs/439364
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Needs to be reverted to code from ubuntu12 and uploaded as ubuntu14.
** Changed in: eucalyptus (Ubuntu Karmic)
Status: New = Triaged
** Changed in: eucalyptus (Ubuntu Karmic)
Milestone: ubuntu-9.10-beta = None
--
1.6~bzr854-0ubuntu13 fails to run instances
Jamie, I continue to have this problem.
Here is an example what I get logged to /var/log/kern.log
type=1503 audit(1254319799.833:61): operation=inode_permission
requested_mask=r:: denied_mask=r:: fsuid=0 name=/bin/bash pid=9551
profile=/sbin/dhclient-script
Could you please elaborate on how to
Public bug reported:
Running 1.6~bzr854-0ubuntu12
Starting an instance of a freshly baked EMI, I get on the NC:
nc.log
[EUCADEBUG ] walrus_request(): wrote 36 bytes in 1 writes
[EUCAERROR ] walrus_request(): server responded with HTTP code 500
[EUCAINFO ] walrus_request(): due to error,
Public bug reported:
Using UEC 20090929 beta candidate on UEC cloud.
Bundling the amd64 image with local kernel and ramdisk works.
Bundling it with uec-images-published kernel and ramdisk fails (see
get-console-output log).
Bundling it with uec-images-published kernel and local ramdisk works.
You may also put this in a file like /etc/tomcat6/policy.d/99custom-
fixes.policy :
grant codeBase file:${catalina.home}/bin/tomcat-juli.jar {
permission java.lang.RuntimePermission setContextClassLoader;
};
... does the job without too widely opening security.
--
Tomcat security
** Attachment added: euca-get-console-output for failed EMI
http://launchpadlibrarian.net/32749737/boot.log
--
Bundling UEC image with provided ramdisk results in an EMI that fails to boot
https://bugs.launchpad.net/bugs/439415
You received this bug notification because you are a member of
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
1.6~bzr854-0ubuntu13 fails to run instances
https://bugs.launchpad.net/bugs/439288
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Some more information.
I did a 20090930.1 CD-based install.
Cluster : no issue. Looking at the registration logs, I remember seeing some
errors, but the final lines all show success with the external IP used, so I
figured everything was ok and fixed.
Node: no issue.
Stopped/started eucalyptus on
severin,
You don't have to do anything on 9.10. 9.04 had logic for handling
ifupdown (which is why you are seeing the problem).
Can you please perform:
$ sudo apport-collect -p apparmor 343898
** Changed in: dhcp3 (Ubuntu)
Status: Fix Released = Incomplete
--
dhclient-script apparmor
Is it possible that, at some point, a walrus registration was attempted
with 'localhost'? If so, you'll need to deregister walrus:
euca_conf --deregister-walrus
and try registering again with a valid public IP. This error is
implying that the system believes that a registered walrus lives on
This is an install from scratch, using CD install. First test was done
with the autoregistration stuff from Dustin. The logs showed the
external IP to be used.
See above, I tried deregister/manual register. It also showed external
IP being used, and also failed. I think there ios something on the
Is this bug only relevant to disk files? I am booting guests fine with
raw disks, albeit LVM-based.
Details:
On a Jaunty KVM host I'm using LVM. When creating a guest I allocated 2
logical volumes (4 GB and 80 GB) to it to be used as raw disks. With
virt-manager I used the first one
Jamie,
I am running jaunty (ie. 9.4) not karmic. BTW. it's an eeePc with custom
kernel. I ran
$ sudo apport-collect -p apparmor 343898
(twice actually) and this is what I got in response
Logging into Launchpad...
Downloading bug...
Bug title: dhclient-script apparmor issues
Collecting apport
Actually, you gave enough information to know what the problem is. The
apparmor profile in 9.04 is specific to the 2.6.28 kernel as included in
Ubuntu. There was a bug in the kernel that is worked around in the
apparmor profile. This is bug #400349. For people who are using a non-
Ubuntu kernel on
** This bug has been marked a duplicate of bug 435061
smbd loses connection on DHCP lease
** This bug is no longer a duplicate of bug 435061
smbd loses connection on DHCP lease
--
Samba session request failure when using IP address
https://bugs.launchpad.net/bugs/437944
You received this
** Package changed: dhcp3 (Ubuntu) = samba (Ubuntu)
** Changed in: samba (Ubuntu)
Assignee: (unassigned) = Chuck Short (zulcss)
--
Karmic Alpha 4 playback stops when playing media stored on samba share
https://bugs.launchpad.net/bugs/420960
You received this bug notification because you
*** This bug is a duplicate of bug 420960 ***
https://bugs.launchpad.net/bugs/420960
** This bug has been marked a duplicate of bug 420960
Karmic Alpha 4 playback stops when playing media stored on samba share
--
smbd loses connection on DHCP lease
https://bugs.launchpad.net/bugs/435061
Ran aswell in with Jaunty
Much simplier solution, even with no connection at all
touch /etc/postfix/main.cf
--
postfix: fatal: /etc/postfix/postfix-script: No such file or directory
https://bugs.launchpad.net/bugs/42947
You received this bug notification because you are a member of Ubuntu
Thierry,
I *definitely* am not reproducing the 127.0.0.1 error. In my nc.log,
I'm seeing:
[Wed Sep 30 17:37:49 2009][008286][EUCAINFO ] from
http://192.168.0.136:8773/services/Walrus/ueckernel/vmlinuz-2.6.31-11-generic.manifest.xml
[Wed Sep 30 17:37:49 2009][008286][EUCAINFO
Actually, the last part of the previous comment about never moving
pending-running might be premature, actually.
Its still working on creating the instance, I think. In the NC, I can
see:
root 17311 17278 3 17:53 ?00:00:16 /bin/dd
Okay, yeah, so my instance runs after a long time:
RESERVATION r-31500705 admin default
INSTANCEi-3BEB06F3 emi-D5871527192.168.0.250 172.19.1.2
running mykey 0 m1.xlarge 2009-09-30T22:37:49.042Z
canyonedge eki-8F0A139D
The lack of networking appears to be a problem in the particular image I
tried (daily UEC build).
When I run bundle and run an image from Eucalyptus, such as:
*
http://eucalyptussoftware.com/downloads/eucalyptus-images/euca-ubuntu-9.04-x86_64.tar.gz
networking comes up just fine!
I'm now
I was able to do this with these instructions:
wget
http://eucalyptussoftware.com/downloads/eucalyptus-images/euca-ubuntu-9.04-x86_64.tar.gz
gunzip euca-ubuntu-9.04-x86_64.tar.gz
tar xvf euca-ubuntu-9.04-x86_64.tar
euca-bundle-image -i
Public bug reported:
Binary package hint: ec2-ami-tools
the ec2-bundle-image and ec2-unbundle-image tools make fifos in /tmp
with names of ec2-bundle-image-digest and ec2-unbundle-image-digest
respectively. This is potentially a security issue, and definitely it
means that 2 processes can't be
** Attachment added: proposed patch
http://launchpadlibrarian.net/32767375/ec2-ami-tools-use-random-mkfifo-name.diff
--
ec2-bundle-image and ec2-unbundle-image use single, static named fifo in /tmp
https://bugs.launchpad.net/bugs/439788
You received this bug notification because you are a
38 matches
Mail list logo
