[Bug 962615] Re: Unable to list volumes after building from snapshot
** Branch linked: lp:~kiall/nova/fix-snapshot-id -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/962615 Title: Unable to list volumes after building from snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/962615/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 939122] Re: floating ips do not display in 'nova list' after association to instance
** Also affects: nova (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/939122 Title: floating ips do not display in 'nova list' after association to instance To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/939122/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 930255] Re: Keystone's precise dbconfig uses incorrect case for roles.
I should probably have mentioned, nova checks these roles in a case sensitive manor. Using the wrong case means the roles simply will not work.. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/930255 Title: Keystone's precise dbconfig uses incorrect case for roles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/930255/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 930255] [NEW] Keystone's precise dbconfig uses incorrect case for roles.
Public bug reported: The recently merged packaging dbconfig uses Admin rather than admin during role creation. See: https://bugs.launchpad.net/devstack/+bug/919373 and https://review.openstack.org/3229 ** Affects: keystone (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/930255 Title: Keystone's precise dbconfig uses incorrect case for roles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/930255/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 912066] Re: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present.
This is a nova bug all right, supplies the incorrect device name in the
ec2 metadata.
Nova supplies the following:
'block-device-mapping': {'ami': 'vda',
'root': '/dev/vda',
'swap': '/dev/vdc'},
When it should supply this:
'block-device-mapping': {'ami': 'vda',
'root': '/dev/vda',
'swap': '/dev/vdb'},
It seems to nova asks libvirt to attach the swap device at /dev/vdc, but
since libvirt+kvm simply uses the supplied device name as an ordering
hint, the device is actually attached at /dev/vdb
** Changed in: nova
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/912066
Title:
/etc/fstab contains incorrect device for swap partition when no
ephemeral disk present.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/912066/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 912066] Re: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present.
I should mention, I believe the fix is for nova to ask for the device to be attached at /dev/vdb when there is no ephemeral disk. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/912066 Title: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/912066/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 912066] Re: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present.
** Also affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/912066 Title: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/912066/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 912066] Re: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present.
Libvirt XML: http://paste.ubuntu.com/807484/ Instance metadata: http://paste.ubuntu.com/807485/ $ ls /dev/vd* /dev/vda /dev/vda1 /dev/vdb $ cat /etc/fstab # /etc/fstab: static file system information. # file system mount point type options dump pass proc/proc proc nodev,noexec,nosuid 0 0 LABEL=cloudimg-rootfs / ext4defaults0 0 /dev/vdcnoneswapsw,comment=cloudconfig 0 0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/912066 Title: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/912066/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 912066] Re: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present.
$ sudo blkid /dev/vdb /dev/vdb: UUID=3447f2ad-9c81-4b95-ab3d-d5ff7aacbfa6 TYPE=swap -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/912066 Title: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/912066/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 912066] [NEW] /etc/fstab contains incorrect device for swap partition when no ephemeral disk present.
Public bug reported: On OpenStack using a flavor with no ephemeral storage, but with swap space, cloud-init creates an invalid /etc/fstab Given this favor (Note: Storage: 0GB and Swap: 2048MB): p1.small: Memory: 3072MB, VCPUS: 4, Storage: 0GB, FlavorID: 15, Swap: 2048MB, RXTX Quota: 0GB, RXTX Cap: 0MB The fstab is generated as: # /etc/fstab: static file system information. # file system mount point type options dump pass proc/proc proc nodev,noexec,nosuid 0 0 LABEL=cloudimg-rootfs / ext4defaults0 0 /dev/vdcnoneswapsw,comment=cloudconfig 0 0 While the devices are (/dev/vdb is the swap): # ls /dev/vd* /dev/vda /dev/vda1 /dev/vdb ** Affects: cloud-init Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/912066 Title: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/912066/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 912066] Re: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present.
Also, This is on the Oneiric cloud-image. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/912066 Title: /etc/fstab contains incorrect device for swap partition when no ephemeral disk present. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/912066/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 870168] Re: Kernel Oops - Oneiric KVM/OpenStack triggers 'Unable to handle kernel NULL pointer deference'
Okay - I've managed to get about 24 hours without a panic! (With the stock oneiric packages ie 3.0 kernel etc) To fix this issue, I purged all OpenStack components, Wiped the OpenStack database and re-installed. I say fix because obviously the Oops should never have occurred at all, regardless of my OpenStack mis-configuration. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/870168 Title: Kernel Oops - Oneiric KVM/OpenStack triggers 'Unable to handle kernel NULL pointer deference' To manage notifications about this bug go to: https://bugs.launchpad.net/kvm/+bug/870168/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 870168] Re: Kernel Oops - Oneiric KVM/OpenStack triggers 'Unable to handle kernel NULL pointer deference'
** Also affects: kvm Importance: Undecided Status: New ** Also affects: kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/870168 Title: Kernel Oops - Oneiric KVM/OpenStack triggers 'Unable to handle kernel NULL pointer deference' To manage notifications about this bug go to: https://bugs.launchpad.net/kvm/+bug/870168/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 870168] Re: Kernel Oops - Oneiric KVM/OpenStack triggers 'Unable to handle kernel NULL pointer deference'
Just tested with the mainline 3.0.6-030006-generic kernel, still panicking... http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0.6-oneiric/linux- image-3.0.6-030006-generic_3.0.6-030006.201110050043_amd64.deb and ... Just tested with the mainline 3.1.0-0301rc9-generic kernel, this kernel after a quick test seems okay! Normally, I would have managed to crash the server by starting/stopping/starting/stopping this many VMs (Until now, 4x starts has always triggered the issue .. I'm on about 15 now.. ) http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0.6-oneiric/linux- image-3.0.6-030006-generic_3.0.6-030006.201110050043_amd64.deb -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/870168 Title: Kernel Oops - Oneiric KVM/OpenStack triggers 'Unable to handle kernel NULL pointer deference' To manage notifications about this bug go to: https://bugs.launchpad.net/kvm/+bug/870168/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 870168] Re: Kernel Oops - Oneiric KVM/OpenStack triggers 'Unable to handle kernel NULL pointer deference'
Damn - 3.1.0-0301rc9-generic lasted *much* longer, but eventually ended with another Oops... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/870168 Title: Kernel Oops - Oneiric KVM/OpenStack triggers 'Unable to handle kernel NULL pointer deference' To manage notifications about this bug go to: https://bugs.launchpad.net/kvm/+bug/870168/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 697601] Re: Keepalived version bump to 1.2.1
++ We're building our own packages for IPv6 Support... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/697601 Title: Keepalived version bump to 1.2.1 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 680301] Re: DNS Search Domain in instance /etc/resov.conf should be set by DHCP
Its actually simpler than that :)
L1032 of net/vnetwork.c is
fprintf(fp, subnet %s netmask %s {\n option subnet-mask %s;\n option
broadc .
change it to ..
fprintf(fp, subnet %s netmask %s {\n option domain-name
\eucalyptus.internal\;\n option subnet-mask %s;\n option broadc ...
and recompile ..
Also - that user-data script you have wont work thanks to default-lease-time
1200; .. 20 mins later your changes are reverted...
--
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/680301
Title:
DNS Search Domain in instance /etc/resov.conf should be set by DHCP
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 680301] Re: DNS Search Domain in instance /etc/resov.conf should be set by DHCP
Also re (I'm using the CLC private IP, because when using the public IP, the returning packets are from the local address, and dns doesn't like it.) .. Thats a mix of two issues i think .. Lets say your instance FQDN is euca-172-19-1-2.eucalyptus.internal / euca-10-2-2-110.eucalyptus.uec.domain.com (i.e in the admin GUI, you set the domain to be uec.domain.com) You have to delegate uec.domain.com to the CLC's public IP in domain.com's DNS records, and on you're local resolver, delagate internal to the CLC's public IP ... This is the only way I've managed to hack euca's DNS setup to work.. The second possible part of that issue is traffic returning from the wrong interface - thats hairpin NAT not being applied correctly. I have another 1 line patch here for this https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/676167 and -- 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/680301 Title: DNS Search Domain in instance /etc/resov.conf should be set by DHCP -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 680301] Re: DNS Search Domain in instance /etc/resov.conf should be set by DHCP
Aha - I didn't noticed it was /etc/dhcp3/dhclient.conf you were editing,
rather than /etc/resolv.conf
Re the change to net/vnetwork.c .. The only config option that would
require that line to change (when DNS is delegated correctly) is when
DISABLE_DNS=Y it should use the original version .. No need for new
config options etc etc..
if (DISABLE_DNS == 'Y') {
fprintf(fp, subnet %s netmask %s {\n option subnet-mask %s;\n option
broadc .
}
else
{
fprintf(fp, subnet %s netmask %s {\n option domain-name
\eucalyptus.internal\;\n option subnet-mask %s;\n option broadc ...
}
Also .. really .. the CLC should not be listed in the nodes
/etc/resolv.conf at all - its an authoritative name server rather than a
recursive name server ..
--
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/680301
Title:
DNS Search Domain in instance /etc/resov.conf should be set by DHCP
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 663920] Re: public IPs unroutable from instances
I believe this is the same issue as https://bugs.launchpad.net/eucalyptus/+bug/676167 I've been told that issue is fixed in the nightly builds.. -- 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/663920 Title: public IPs unroutable from instances -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 676832] Re: Ghost instance using a slot + elastic IP
I should have also mentioned - the Ghost instance (i-307905AD) was a real instance that had been terminated, possibly before it had left the pending state. -- Ghost instance using a slot + elastic IP https://bugs.launchpad.net/bugs/676832 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 676721] [NEW] Security Group names differ between DescribeInstancesResponse and RunInstancesResponse API calls
Public bug reported: Assuming the username kiall and security group app the XML responses differ between DescribeInstances and RunInstances. Attached are the full XML responses. Describe Instances Response shows: groupSet item groupIdapp/groupId /item /groupSet Run Instances Response shows: groupSet item groupIdkiall-app/groupId /item /groupSet ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: eucalyptus-cloud 2.0+bzr1241-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-22.35-server 2.6.35.4 Uname: Linux 2.6.35-22-server x86_64 .etc.eucalyptus.eucalyptus.cc.conf: CC_NAME=lmst01 Architecture: amd64 Date: Wed Nov 17 22:07:13 2010 InstallationMedia: Ubuntu-Server 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: eucalyptus ** Affects: eucalyptus Importance: Undecided Status: New ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- Security Group names differ between DescribeInstancesResponse and RunInstancesResponse API calls https://bugs.launchpad.net/bugs/676721 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 676721] Re: Security Group names differ between DescribeInstancesResponse and RunInstancesResponse API calls
** Attachment added: DescribeInstancesResponse https://bugs.launchpad.net/bugs/676721/+attachment/1736591/+files/DescribeInstancesResponse.txt -- Security Group names differ between DescribeInstancesResponse and RunInstancesResponse API calls https://bugs.launchpad.net/bugs/676721 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 676721] Re: Security Group names differ between DescribeInstancesResponse and RunInstancesResponse API calls
** Attachment added: RunInstancesResponse https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/676721/+attachment/1736596/+files/RunInstancesResponse.txt ** Also affects: eucalyptus Importance: Undecided Status: New -- Security Group names differ between DescribeInstancesResponse and RunInstancesResponse API calls https://bugs.launchpad.net/bugs/676721 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 676819] [NEW] Attaching a volume to a pending instance claims success, but never attaches.
Public bug reported: Attaching a volume to a pending instance claims success (via euca2ools, and the API) but never attaches to the instance. This may be a KVM only issue. As its pretty easy to reproduce, I haven't attached much in the way of detail - let me know if you need any specific info. Command Line usage, assuming i-307905AD is in the pending state: $ euca-attach-volume -d /dev/vda -i i-307905AD vol-59820625 VOLUME vol-59820625 Also, this possibly only occurs very early (first 5 seconds) of the pending state. The same command succeeds if you wait for the instance to arrive at the available status. Eucalyptus: Version: 2.0+bzr1241-0ubuntu4 Euca2ools: Version: 1.2-0ubuntu11 ** Affects: eucalyptus Importance: Undecided Status: New ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Also affects: eucalyptus Importance: Undecided Status: New ** Description changed: ** Description changed: Attaching a volume to a pending instance claims success (via euca2ools, and the API) but never attaches to the instance. This may be a KVM only issue. As its pretty easy to reproduce, I haven't attached much in the way of detail - let me know if you need any specific info. - Command Line usage, assuming i-307905AD is in the pending state - + Command Line usage, assuming i-307905AD is in the pending state: + + $ euca-attach-volume -d /dev/vda -i i-307905AD vol-59820625 + VOLUMEvol-59820625 + Also, this possibly only occurs very early (first 5 seconds) of the pending state. The same command succeeds if you wait for the instance to arrive at the available status. - $ euca-attach-volume -d /dev/vda -i i-307905AD vol-59820625 - VOLUMEvol-59820625 - Eucalyptus: Version: 2.0+bzr1241-0ubuntu4 Euca2ools: Version: 1.2-0ubuntu11 -- Attaching a volume to a pending instance claims success, but never attaches. https://bugs.launchpad.net/bugs/676819 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 676819] Re: Attaching a volume to a pending instance claims success, but never attaches.
** Description changed: Attaching a volume to a pending instance claims success (via euca2ools, and the API) but never attaches to the instance. This may be a KVM only issue. As its pretty easy to reproduce, I haven't attached much in the way of detail - let me know if you need any specific info. Command Line usage, assuming i-307905AD is in the pending state: $ euca-attach-volume -d /dev/vda -i i-307905AD vol-59820625 VOLUMEvol-59820625 Also, this possibly only occurs very early (first 5 seconds) of the pending state. The same command succeeds if you wait for the instance to - arrive at the available status. + arrive at the running status. Eucalyptus: Version: 2.0+bzr1241-0ubuntu4 Euca2ools: Version: 1.2-0ubuntu11 -- Attaching a volume to a pending instance claims success, but never attaches. https://bugs.launchpad.net/bugs/676819 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 676832] [NEW] Ghost instance using a slot + elastic IP
Public bug reported: With a single instance running, 2 instance slots are used up and an elastic IP is in-use by a ghost instance.. I can confirm that there is only a single kvm process on the NC, and eucalyptus seems to know nothing about the instance other than its reserved an IP. Other than this, I really have no info on how this occurred. I'm really just filing this here so its logged! Also - I have the NC logs saved - but there pretty large (20MB total). I'll attach if LP lets me! ki...@wk08-lmst:~/Desktop/CloudConfig$ euca-describe-availability-zones verbose AVAILABILITYZONElmst01 10.2.1.4 AVAILABILITYZONE|- vm types free / max cpu ram disk AVAILABILITYZONE|- m1.small 0021 / 0023 1512 5 AVAILABILITYZONE|- c1.medium0005 / 0006 2 1740 5 AVAILABILITYZONE|- m1.large / 0001 2 7680 5 AVAILABILITYZONE|- m1.xlarge / 4 15360 5 AVAILABILITYZONE|- c1.xlarge / 8 15361 5 ki...@wk08-lmst:~/Desktop/CloudConfig$ euca-describe-instances RESERVATION r-371406C3 kiall phostr-app INSTANCEi-456F080E emi-077E15DD euca-172-19-12-66.eucalyptus.euca.managedit.ie euca-172-19-12-66.eucalyptus.internal running kiall 0 ki...@wk08-lmst:~/Desktop/CloudConfig$ euca-describe-addresses ... SNIP ... ADDRESS 10.2.6.108 i-307905AD (kiall) ... SNIP ... ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: eucalyptus-cloud 2.0+bzr1241-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-22.35-server 2.6.35.4 Uname: Linux 2.6.35-22-server x86_64 .etc.eucalyptus.eucalyptus.cc.conf: CC_NAME=lmst01 Architecture: amd64 Date: Thu Nov 18 06:22:18 2010 InstallationMedia: Ubuntu-Server 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: eucalyptus ** Affects: eucalyptus Importance: Undecided Status: New ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- Ghost instance using a slot + elastic IP https://bugs.launchpad.net/bugs/676832 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 676832] Re: Ghost instance using a slot + elastic IP
** Attachment added: NC axis2c.log https://bugs.launchpad.net/bugs/676832/+attachment/1736917/+files/axis2c.log -- Ghost instance using a slot + elastic IP https://bugs.launchpad.net/bugs/676832 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 676832] Re: Ghost instance using a slot + elastic IP
** Attachment added: NC euca_test_nc.log https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/676832/+attachment/1736927/+files/euca_test_nc.log -- Ghost instance using a slot + elastic IP https://bugs.launchpad.net/bugs/676832 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 676832] Re: Ghost instance using a slot + elastic IP
** Attachment added: NC httpd-nc_error_log https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/676832/+attachment/1736936/+files/httpd-nc_error_log -- Ghost instance using a slot + elastic IP https://bugs.launchpad.net/bugs/676832 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 676832] Re: Ghost instance using a slot + elastic IP
** Attachment added: NC nc.log https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/676832/+attachment/1736937/+files/nc.log ** Also affects: eucalyptus Importance: Undecided Status: New -- Ghost instance using a slot + elastic IP https://bugs.launchpad.net/bugs/676832 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 676832] Re: Ghost instance using a slot + elastic IP
`service eucalyptus-(nc|walrus|sc|cloud|cc) restart` each had no effect... `service eucalyptus restart` free'd the IP.. -- Ghost instance using a slot + elastic IP https://bugs.launchpad.net/bugs/676832 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 676167] Re: Hairpin NAT on CC disabled - EC2 inconsistency
** Description changed: + + Impact statement: This bug causes several issues warranting a fix in maverick/lucid + + A) Prevents correct communication between instances (eg icmp-reply from priv IP when pub IP was ping'd) + B) Blocks communication to the local instance via its public ip + C) Breaks compatibility with EC2 + + + On EC2, This ping succeeds as would be expected: # ping `curl --quite http://169.254.169.254/2008-02-01/meta-data/public- ipv4` On UEC, The same ping command fails. Additionally on UEC, an instance pinging another instances public IP receives echo-reply's from the second instances private IP, rather than the public IP ping'd. The offending firewall rule (as seen by iptables -L -t nat -n) is: MASQUERADE all -- 172.19.0.0/16 !172.19.0.0/16 When changed to: MASQUERADE all -- 172.19.0.0/160.0.0.0/0 Ping's work as expected (both pings to your local public IP, and other instances public IPs) - The bug appears to be in net/vnetwork.c L200: snprintf(cmd, 256, -A POSTROUTING -d ! %s/%d -s %s/%d -j MASQUERADE, network, slashnet, network, slashnet); should be changed to: snprintf(cmd, 256, -A POSTROUTING -s %s/%d -j MASQUERADE, network, - slashnet, network, slashnet); + slashnet); Hope this makes sense ;) Its been a *long* 2 days. -- Hairpin NAT on CC disabled - EC2 inconsistency https://bugs.launchpad.net/bugs/676167 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 673445] [NEW] USE_VIRTIO_DISK config option ignored for EBS volumes
Public bug reported: Ubuntu 10.10 / eucalyptus-2.0+bzr1241-0ubuntu4 / amd64 After setting USE_VIRTIO_DISK=1 (the default actually..) in /etc/eucalyptus/eucalyptus.conf and performing a clean restart virtio is not used while attaching an EBS volume. I discovered this due to a related bug preventing non-virtio volumes from attaching correcting until after the instance reboots (I'll file this one as soon as I find out if its in kvm or ecua!) I made a *very* dirty hack to node/handlers_kvm.c on L452 / L459 to ensure bus='virtio' was added to the XML .. suddenly it works :) providing an /dev/vda (I'd prefer the device name I specified .. but one step at a time!) ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Tags: ebs uec -- USE_VIRTIO_DISK config option ignored for EBS volumes https://bugs.launchpad.net/bugs/673445 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 673445] Re: USE_VIRTIO_DISK config option ignored for EBS volumes
** Patch added: My *dirty* patch that intentionally breaks correct behavior in order to verify the wrong branch of the if/else was being executed https://bugs.launchpad.net/bugs/673445/+attachment/1728847/+files/euca.diff -- USE_VIRTIO_DISK config option ignored for EBS volumes https://bugs.launchpad.net/bugs/673445 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 673445] Re: USE_VIRTIO_DISK config option ignored for EBS volumes
And .. As always with filing a bug. I just noticed a mistake on my part! L436 of node/handlers_kvm.c forces the use of a non-virtio mount thanks to me specifying a sdX device name rather than vdX .. I'll dig around for the close button! -- USE_VIRTIO_DISK config option ignored for EBS volumes https://bugs.launchpad.net/bugs/673445 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 432154] Re: dynamic block device attach/detach not functional with karmic KVM
Yes - 100% sure. I've since discovered that using /dev/vdX works without a reboot, while /dev/sdX does not work until after a reboot! vdX triggers the use of virtio, while sdX uses the standard method .. whatever that is! I stopped digging once i got it working with vdX :) -- dynamic block device attach/detach not functional with karmic KVM https://bugs.launchpad.net/bugs/432154 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 432154] Re: dynamic block device attach/detach not functional with karmic KVM
@Wolfgang: Yes - Specifying, for example, /dev/vda triggers the use of virtio over the standard - and works exactly as you would expect EBS volumes to :) There *is* still a bug preventing /dev/sdX from working .. but I've sank too much time into finding it at the moment, I'll probably dig in again later. -- dynamic block device attach/detach not functional with karmic KVM https://bugs.launchpad.net/bugs/432154 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 432154] Re: dynamic block device attach/detach not functional with karmic KVM
@Wolfgang I believe this is still an issue in maverick/10.10 aswell. I can attach a volume with UEC (10.10 metal and 10.10 instance). If you issue a `shutdown -r now` within the instance, the volume will be attached after the reboot... just spent about 8 hours getting that far! -- dynamic block device attach/detach not functional with karmic KVM https://bugs.launchpad.net/bugs/432154 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
