[Bug 1240983] Re: Can't upgrade from quantal to saucy
Thanks Brian, I will do that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240983 Title: Can't upgrade from quantal to saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1240983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240983] [NEW] Can't upgrade from quantal to saucy
Public bug reported: When I try to upgrade from quantal to saucy it fails with Can't calculate upgrade. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Thu Oct 17 08:33:31 2013 InstallationDate: Installed on 2012-05-25 (509 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to raring on 2013-10-17 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240983 Title: Can't upgrade from quantal to saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1240983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 417757] Re: [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups
Is there a list of routers that work? -- [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups https://bugs.launchpad.net/bugs/417757 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.com/mailman/listinfo/ubuntu-bugs
[Bug 417757] Re: [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups
or what can a consumer look for to find a router that works? -- [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups https://bugs.launchpad.net/bugs/417757 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.com/mailman/listinfo/ubuntu-bugs
[Bug 417757] Re: [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups
Would there be any advantage to installing DD-WRT or some such to a problem router? -- [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups https://bugs.launchpad.net/bugs/417757 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.com/mailman/listinfo/ubuntu-bugs
[Bug 470823] Re: seahorse-agent assert failure: ERROR:iop-profiles.c:606:IOP_generate_profiles: assertion failed: (obj (obj-profile_list == NULL) obj-orb)
** Attachment added: CoreDump.gz http://launchpadlibrarian.net/34956029/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/34956030/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/34956031/Disassembly.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/34956032/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/34956033/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/34956035/Registers.txt ** Attachment added: Stacktrace.txt http://launchpadlibrarian.net/34956036/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/34956037/ThreadStacktrace.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/34956038/XsessionErrors.txt ** Visibility changed to: Public -- seahorse-agent assert failure: ERROR:iop-profiles.c:606:IOP_generate_profiles: assertion failed: (obj (obj-profile_list == NULL) obj-orb) https://bugs.launchpad.net/bugs/470823 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.com/mailman/listinfo/ubuntu-bugs
[Bug 452185] Re: can't access SC volumes in a UEC instance
Reinstalling with guided partitioning did not fix the problem, so it wasn't XFS. -- 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 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 452185] Re: can't access SC volumes in a UEC instance
Here's my whole process, using the latest Karmic RC and the RC UEC images: This is how I packaged the RC images : nimbusad...@nimbus:~$ euca-bundle-image -i karmic-uec-amd64-vmlinuz-virtual --k ernel true Checking image Tarring image Encrypting image Splitting image... Part: karmic-uec-amd64-vmlinuz-virtual.part.0 Generating manifest nimbusad...@nimbus:~$ euca-upload-bundle -b uecrckernel -m /tmp/karmic-uec-amd6 4-vmlinuz-virtual.manifest.xml Checking bucket: uecrckernel Creating bucket: uecrckernel Uploading manifest file Uploading part: karmic-uec-amd64-vmlinuz-virtual.part.0 Uploaded image as uecrckernel/karmic-uec-amd64-vmlinuz-virtual.manifest.xml nimbusad...@nimbus:~$ euca-register uecrckernel/karmic-uec-amd64-vmlinuz-virtua l.manifest.xml IMAGE eki-A8AB1882 nimbusad...@nimbus:~$ euca-bundle-image -i karmic-uec-amd64-initrd-virtual --ra mdisk true Checking image Tarring image Encrypting image Splitting image... Part: karmic-uec-amd64-initrd-virtual.part.0 Generating manifest nimbusad...@nimbus:~$ euca-upload-bundle -b uecrcramdisk -m /tmp/karmic-uec-amd 64-initrd-virtual.manifest.xml Checking bucket: uecrcramdisk Creating bucket: uecrcramdisk Uploading manifest file Uploading part: karmic-uec-amd64-initrd-virtual.part.0 Uploaded image as uecrcramdisk/karmic-uec-amd64-initrd-virtual.manifest.xml nimbusad...@nimbus:~$ euca-register uecrcramdisk/karmic-uec-amd64-initrd-virtua l.manifest.xml IMAGE eri-A52B1860 nimbusad...@nimbus:~$ euca-bundle-image -i karmic-uec-amd64.img --kernel eki-A8 AB1882 --ramdisk eri-A52B1860 Checking image Tarring image Encrypting image Splitting image... Part: karmic-uec-amd64.img.part.0 Part: karmic-uec-amd64.img.part.1 Part: karmic-uec-amd64.img.part.2 Part: karmic-uec-amd64.img.part.3 Part: karmic-uec-amd64.img.part.4 Part: karmic-uec-amd64.img.part.5 Part: karmic-uec-amd64.img.part.6 Part: karmic-uec-amd64.img.part.7 Part: karmic-uec-amd64.img.part.8 Part: karmic-uec-amd64.img.part.9 Part: karmic-uec-amd64.img.part.10 Part: karmic-uec-amd64.img.part.11 Part: karmic-uec-amd64.img.part.12 Part: karmic-uec-amd64.img.part.13 Part: karmic-uec-amd64.img.part.14 Part: karmic-uec-amd64.img.part.15 Part: karmic-uec-amd64.img.part.16 Part: karmic-uec-amd64.img.part.17 Generating manifest nimbusad...@nimbus:~$ euca-upload-bundle -b uecrckernel -m /tmp/image.manifest. xml Invalid manifest nimbusad...@nimbus:~$ euca-upload-bundle -b uecrckernel -m /tmp/karmic-uec-amd6 4.img.manifest.xml Checking bucket: uecrckernel Uploading manifest file Uploading part: karmic-uec-amd64.img.part.0 Uploading part: karmic-uec-amd64.img.part.1 Uploading part: karmic-uec-amd64.img.part.2 Uploading part: karmic-uec-amd64.img.part.3 Uploading part: karmic-uec-amd64.img.part.4 Uploading part: karmic-uec-amd64.img.part.5 Uploading part: karmic-uec-amd64.img.part.6 Uploading part: karmic-uec-amd64.img.part.7 Uploading part: karmic-uec-amd64.img.part.8 Uploading part: karmic-uec-amd64.img.part.9 Uploading part: karmic-uec-amd64.img.part.10 Uploading part: karmic-uec-amd64.img.part.11 Uploading part: karmic-uec-amd64.img.part.12 Uploading part: karmic-uec-amd64.img.part.13 Uploading part: karmic-uec-amd64.img.part.14 Uploading part: karmic-uec-amd64.img.part.15 Uploading part: karmic-uec-amd64.img.part.16 Uploading part: karmic-uec-amd64.img.part.17 Uploaded image as uecrckernel/karmic-uec-amd64.img.manifest.xml nimbusad...@nimbus:~$ euca-register uecrckernel/karmic-uec-amd64.img.manifest.x ml IMAGE emi-76171375 Here's where I fired up the instance: euca-run-instances -k auueckey emi-76171375 -t c1.medium Here's what it looks like now: RESERVATION r-3221069D admin default INSTANCEi-4F8E099C emi-76171375131.204.2.112 172.19.1.2 running auueckey0 c1.medium 2009-10-23T12:50:06.685Z AUUEC eki-A8AB1882eri-A52B1860 Here I create my volume: euca-create-volume -s 1 -z AUUEC VOLUME vol-329904A41 creating2009-10-23T12:53:53.061Z euca-describe-volumes VOLUME vol-329904A4 1 AUUEC available 2009-10-23T12:53:53.061Z Here I attach the volume: euca-attach-volume -i i-4F8E099C -d sdb vol-329904A4 VOLUME vol-329904A4 But: euca-describe-volumes VOLUME vol-329904A4 1 AUUEC available 2009-10-23T12:53 In cc.log it says: [Fri Oct 23 07:56:11 2009][001486][EUCAERROR ] bad input params to vnetAttachTunnels() [Fri Oct 23 07:56:11 2009][001486][EUCADEBUG ] failed to attach tunnels for vlan 10 during maintainNetworkState() [Fri Oct 23 07:56:11 2009][001486][EUCAERROR ] network state maintainance failed -- 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 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:
[Bug 452185] Re: can't access SC volumes in a UEC instance
Sure. euca-attach-volume -i i-500E09A7 -d /dev/sdb vol-329904A4 VOLUME vol-329904A4 euca-describe-volumes VOLUME vol-329904A4 1 AUUEC available 2009-10-23T12:53:53.061Z [Fri Oct 23 09:27:01 2009][003011][EUCADEBUG ] DescribeNetworks(): done [Fri Oct 23 09:27:01 2009][003011][EUCAERROR ] bad input params to vnetAttachTunnels() [Fri Oct 23 09:27:01 2009][003011][EUCADEBUG ] failed to attach tunnels for vlan 10 during maintainNetworkState() -- 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 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 452185] Re: can't access SC volumes in a UEC instance
I figured out the problem. I was looking at the web interface, under configuration in the Storage Controller section, the IP address there was my public IP address and the ethernet device was my public ethernet interface. When I changed the IP address to my private IP address and private IP address, and I created a brand new volume (the old volume would not work) this is what happened: euca-create-volume -s 1 -z AUUEC VOLUME vol-32EA04B01 creating2009-10-23T14:41:47.375Z euca-attach-volume -i i-500E09A7 -d /de v/sdb vol-32EA04B0 euca-describe-volumes VOLUME vol-32EA04B0 1 AUUEC in-use 2009-10-23T14:41:47.375Z ATTACHMENT vol-32EA04B0i-500E09A7 /dev/sdb 2009-10-23T14:42:10.274Z Then I could go in my instance, see the volume, fdisk it, create a partition, format it , mount it and create/delete files on it. I am happy! However, the question now becomes - why did the Storage Controller register itself on my public IP and public interface as opposed to my private IP and private interface? -- 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 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 459194] [NEW] SC must be re-registered to the private NIC/IP after installation
Public bug reported: After UEC installation on a system with a separate physical NIC that attaches to the private network that the NCs (node controllers) are on, the user must change the registration of the SC (storage controller) to use the private interface/IP. This can be done from the web interface under Configuration, Clusters, Storage Controllers. This can also be done from the command line using euca_conf --deregester-sc public IP, followed by a euca_conf register-sc name private IP. Be sure to change both the IP address and the name of the interface. Also, any volumes created before this change will need to be removed using euca-delete- volume because they will not work and will simply take up space on your system. ** Affects: eucalyptus Importance: Undecided Status: New ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Also affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- SC must be re-registered to the private NIC/IP after installation https://bugs.launchpad.net/bugs/459194 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 452185] Re: can't access SC volumes in a UEC instance
Reinstalling with guided partitioning did not fix the problem, so it wasn't XFS. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452185] Re: can't access SC volumes in a UEC instance
Here's my whole process, using the latest Karmic RC and the RC UEC images: This is how I packaged the RC images : nimbusad...@nimbus:~$ euca-bundle-image -i karmic-uec-amd64-vmlinuz-virtual --k ernel true Checking image Tarring image Encrypting image Splitting image... Part: karmic-uec-amd64-vmlinuz-virtual.part.0 Generating manifest nimbusad...@nimbus:~$ euca-upload-bundle -b uecrckernel -m /tmp/karmic-uec-amd6 4-vmlinuz-virtual.manifest.xml Checking bucket: uecrckernel Creating bucket: uecrckernel Uploading manifest file Uploading part: karmic-uec-amd64-vmlinuz-virtual.part.0 Uploaded image as uecrckernel/karmic-uec-amd64-vmlinuz-virtual.manifest.xml nimbusad...@nimbus:~$ euca-register uecrckernel/karmic-uec-amd64-vmlinuz-virtua l.manifest.xml IMAGE eki-A8AB1882 nimbusad...@nimbus:~$ euca-bundle-image -i karmic-uec-amd64-initrd-virtual --ra mdisk true Checking image Tarring image Encrypting image Splitting image... Part: karmic-uec-amd64-initrd-virtual.part.0 Generating manifest nimbusad...@nimbus:~$ euca-upload-bundle -b uecrcramdisk -m /tmp/karmic-uec-amd 64-initrd-virtual.manifest.xml Checking bucket: uecrcramdisk Creating bucket: uecrcramdisk Uploading manifest file Uploading part: karmic-uec-amd64-initrd-virtual.part.0 Uploaded image as uecrcramdisk/karmic-uec-amd64-initrd-virtual.manifest.xml nimbusad...@nimbus:~$ euca-register uecrcramdisk/karmic-uec-amd64-initrd-virtua l.manifest.xml IMAGE eri-A52B1860 nimbusad...@nimbus:~$ euca-bundle-image -i karmic-uec-amd64.img --kernel eki-A8 AB1882 --ramdisk eri-A52B1860 Checking image Tarring image Encrypting image Splitting image... Part: karmic-uec-amd64.img.part.0 Part: karmic-uec-amd64.img.part.1 Part: karmic-uec-amd64.img.part.2 Part: karmic-uec-amd64.img.part.3 Part: karmic-uec-amd64.img.part.4 Part: karmic-uec-amd64.img.part.5 Part: karmic-uec-amd64.img.part.6 Part: karmic-uec-amd64.img.part.7 Part: karmic-uec-amd64.img.part.8 Part: karmic-uec-amd64.img.part.9 Part: karmic-uec-amd64.img.part.10 Part: karmic-uec-amd64.img.part.11 Part: karmic-uec-amd64.img.part.12 Part: karmic-uec-amd64.img.part.13 Part: karmic-uec-amd64.img.part.14 Part: karmic-uec-amd64.img.part.15 Part: karmic-uec-amd64.img.part.16 Part: karmic-uec-amd64.img.part.17 Generating manifest nimbusad...@nimbus:~$ euca-upload-bundle -b uecrckernel -m /tmp/image.manifest. xml Invalid manifest nimbusad...@nimbus:~$ euca-upload-bundle -b uecrckernel -m /tmp/karmic-uec-amd6 4.img.manifest.xml Checking bucket: uecrckernel Uploading manifest file Uploading part: karmic-uec-amd64.img.part.0 Uploading part: karmic-uec-amd64.img.part.1 Uploading part: karmic-uec-amd64.img.part.2 Uploading part: karmic-uec-amd64.img.part.3 Uploading part: karmic-uec-amd64.img.part.4 Uploading part: karmic-uec-amd64.img.part.5 Uploading part: karmic-uec-amd64.img.part.6 Uploading part: karmic-uec-amd64.img.part.7 Uploading part: karmic-uec-amd64.img.part.8 Uploading part: karmic-uec-amd64.img.part.9 Uploading part: karmic-uec-amd64.img.part.10 Uploading part: karmic-uec-amd64.img.part.11 Uploading part: karmic-uec-amd64.img.part.12 Uploading part: karmic-uec-amd64.img.part.13 Uploading part: karmic-uec-amd64.img.part.14 Uploading part: karmic-uec-amd64.img.part.15 Uploading part: karmic-uec-amd64.img.part.16 Uploading part: karmic-uec-amd64.img.part.17 Uploaded image as uecrckernel/karmic-uec-amd64.img.manifest.xml nimbusad...@nimbus:~$ euca-register uecrckernel/karmic-uec-amd64.img.manifest.x ml IMAGE emi-76171375 Here's where I fired up the instance: euca-run-instances -k auueckey emi-76171375 -t c1.medium Here's what it looks like now: RESERVATION r-3221069D admin default INSTANCEi-4F8E099C emi-76171375131.204.2.112 172.19.1.2 running auueckey0 c1.medium 2009-10-23T12:50:06.685Z AUUEC eki-A8AB1882eri-A52B1860 Here I create my volume: euca-create-volume -s 1 -z AUUEC VOLUME vol-329904A41 creating2009-10-23T12:53:53.061Z euca-describe-volumes VOLUME vol-329904A4 1 AUUEC available 2009-10-23T12:53:53.061Z Here I attach the volume: euca-attach-volume -i i-4F8E099C -d sdb vol-329904A4 VOLUME vol-329904A4 But: euca-describe-volumes VOLUME vol-329904A4 1 AUUEC available 2009-10-23T12:53 In cc.log it says: [Fri Oct 23 07:56:11 2009][001486][EUCAERROR ] bad input params to vnetAttachTunnels() [Fri Oct 23 07:56:11 2009][001486][EUCADEBUG ] failed to attach tunnels for vlan 10 during maintainNetworkState() [Fri Oct 23 07:56:11 2009][001486][EUCAERROR ] network state maintainance failed -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452185] Re: can't access SC volumes in a UEC instance
Sure. euca-attach-volume -i i-500E09A7 -d /dev/sdb vol-329904A4 VOLUME vol-329904A4 euca-describe-volumes VOLUME vol-329904A4 1 AUUEC available 2009-10-23T12:53:53.061Z [Fri Oct 23 09:27:01 2009][003011][EUCADEBUG ] DescribeNetworks(): done [Fri Oct 23 09:27:01 2009][003011][EUCAERROR ] bad input params to vnetAttachTunnels() [Fri Oct 23 09:27:01 2009][003011][EUCADEBUG ] failed to attach tunnels for vlan 10 during maintainNetworkState() -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452185] Re: can't access SC volumes in a UEC instance
I figured out the problem. I was looking at the web interface, under configuration in the Storage Controller section, the IP address there was my public IP address and the ethernet device was my public ethernet interface. When I changed the IP address to my private IP address and private IP address, and I created a brand new volume (the old volume would not work) this is what happened: euca-create-volume -s 1 -z AUUEC VOLUME vol-32EA04B01 creating2009-10-23T14:41:47.375Z euca-attach-volume -i i-500E09A7 -d /de v/sdb vol-32EA04B0 euca-describe-volumes VOLUME vol-32EA04B0 1 AUUEC in-use 2009-10-23T14:41:47.375Z ATTACHMENT vol-32EA04B0i-500E09A7 /dev/sdb 2009-10-23T14:42:10.274Z Then I could go in my instance, see the volume, fdisk it, create a partition, format it , mount it and create/delete files on it. I am happy! However, the question now becomes - why did the Storage Controller register itself on my public IP and public interface as opposed to my private IP and private interface? -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452185] Re: can't access SC volumes in a UEC instance
** Changed in: eucalyptus (Ubuntu) Status: Incomplete = Invalid ** Changed in: eucalyptus Status: Incomplete = Invalid -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 459194] [NEW] SC must be re-registered to the private NIC/IP after installation
Public bug reported: After UEC installation on a system with a separate physical NIC that attaches to the private network that the NCs (node controllers) are on, the user must change the registration of the SC (storage controller) to use the private interface/IP. This can be done from the web interface under Configuration, Clusters, Storage Controllers. This can also be done from the command line using euca_conf --deregester-sc public IP, followed by a euca_conf register-sc name private IP. Be sure to change both the IP address and the name of the interface. Also, any volumes created before this change will need to be removed using euca-delete- volume because they will not work and will simply take up space on your system. ** Affects: eucalyptus Importance: Undecided Status: New ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Also affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- SC must be re-registered to the private NIC/IP after installation https://bugs.launchpad.net/bugs/459194 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.com/mailman/listinfo/ubuntu-bugs
[Bug 452185] Re: can't access SC volumes in a UEC instance
My host systems use XFS filesystem - could this cause this problem? -- 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 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 452185] Re: can't access SC volumes in a UEC instance
My host systems use XFS filesystem - could this cause this problem? -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452185] Re: can't access SC volumes in a UEC instance
** Changed in: eucalyptus Status: Invalid = Incomplete ** Changed in: eucalyptus (Ubuntu) Status: Invalid = Incomplete -- 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 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 452185] Re: can't access SC volumes in a UEC instance
I am still having this problem. I am using the latest uec-image from 10-20. If I do a lsmod | grep acpiphp I get acpiphp25180 0 so the module is running. I'm no longer using a bridge on my CC - I am using the setup from 10-19 daily server ISOs. I've tried euca-attach-volume -i i-46C508A6 -d /dev/sdb vol-32BA04A7 and euca-attach-volume -i i-46C508A6 -d sdb vol-32BA04A7 both return VOLUME vol-32BA04A7 then in both cases if I do a euca-describe-volumes I get VOLUME vol-32BA04A7 10 AUUEC available 2009-10-20T03:27:55.218Z it shows available which tells me it didn't attach to my instance, to check I look into the instance and sure enough the volume device is not there. I check the nc.log, and I don't find anything of relevance there, which leads me to the cc.log , where I find this: [Mon Oct 19 22:57:01 2009][001385][EUCAERROR ] bad input params to vnetAttachTunnels() [Mon Oct 19 22:57:01 2009][001385][EUCADEBUG ] failed to attach tunnels for vlan 10 during maintainNetworkState() [Mon Oct 19 22:57:01 2009][001385][EUCAERROR ] network state maintainance failed -- 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 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 452185] Re: can't access SC volumes in a UEC instance
** Changed in: eucalyptus Status: Invalid = Incomplete ** Changed in: eucalyptus (Ubuntu) Status: Invalid = Incomplete -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452185] Re: can't access SC volumes in a UEC instance
I am still having this problem. I am using the latest uec-image from 10-20. If I do a lsmod | grep acpiphp I get acpiphp25180 0 so the module is running. I'm no longer using a bridge on my CC - I am using the setup from 10-19 daily server ISOs. I've tried euca-attach-volume -i i-46C508A6 -d /dev/sdb vol-32BA04A7 and euca-attach-volume -i i-46C508A6 -d sdb vol-32BA04A7 both return VOLUME vol-32BA04A7 then in both cases if I do a euca-describe-volumes I get VOLUME vol-32BA04A7 10 AUUEC available 2009-10-20T03:27:55.218Z it shows available which tells me it didn't attach to my instance, to check I look into the instance and sure enough the volume device is not there. I check the nc.log, and I don't find anything of relevance there, which leads me to the cc.log , where I find this: [Mon Oct 19 22:57:01 2009][001385][EUCAERROR ] bad input params to vnetAttachTunnels() [Mon Oct 19 22:57:01 2009][001385][EUCADEBUG ] failed to attach tunnels for vlan 10 during maintainNetworkState() [Mon Oct 19 22:57:01 2009][001385][EUCAERROR ] network state maintainance failed -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452185] [NEW] can't access SC volumes in a UEC instance
Public bug reported: When I try euca-attach-volume -i instanceid -d devicename scvolumename it returns scvolumename but when I ssh into the instance, I can't access the scvolume, it doesn't show up under /dev, fdisk /dev/devicename doesn't work. and if I do euca-describe-volumes the volume has a status of available. ** Affects: eucalyptus Importance: Undecided Status: New ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Also affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- 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 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 452185] Re: can't access SC volumes in a UEC instance
This is with package version 1.6~bzr931-0ubuntu2 -- 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 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 452185] Re: can't access SC volumes in a UEC instance
Actually, since my interface to the private subnet is a bridge as required according to the cc.log for MANAGED-NOVLAN which is the default setup using the server CDs, I was told by nekro_ in the #eucalyptus channel that vblade/aoe won't export across a linux bridge :( so I am thinking if you use MANAGED-NOVLAN perhaps SC has to run either on a different machine, or on another interface to the private network on the front-end. -- 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 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 452185] [NEW] can't access SC volumes in a UEC instance
Public bug reported: When I try euca-attach-volume -i instanceid -d devicename scvolumename it returns scvolumename but when I ssh into the instance, I can't access the scvolume, it doesn't show up under /dev, fdisk /dev/devicename doesn't work. and if I do euca-describe-volumes the volume has a status of available. ** Affects: eucalyptus Importance: Undecided Status: New ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Also affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452185] Re: can't access SC volumes in a UEC instance
This is with package version 1.6~bzr931-0ubuntu2 -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452185] Re: can't access SC volumes in a UEC instance
Actually, since my interface to the private subnet is a bridge as required according to the cc.log for MANAGED-NOVLAN which is the default setup using the server CDs, I was told by nekro_ in the #eucalyptus channel that vblade/aoe won't export across a linux bridge :( so I am thinking if you use MANAGED-NOVLAN perhaps SC has to run either on a different machine, or on another interface to the private network on the front-end. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 434043] Re: euca-run-instances emi-xxxxxxxx -k key doesn't start an instance
I think this has been fixed. -- euca-run-instances emi- -k key doesn't start an instance https://bugs.launchpad.net/bugs/434043 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 434036] Re: euca-describe-availability-zones verbose doesn't report the types of instances available
This appears to be fixed. -- 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 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 434043] Re: euca-run-instances emi-xxxxxxxx -k key doesn't start an instance
I think this has been fixed. -- euca-run-instances emi- -k key doesn't start an instance https://bugs.launchpad.net/bugs/434043 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.com/mailman/listinfo/ubuntu-bugs
[Bug 434036] Re: euca-describe-availability-zones verbose doesn't report the types of instances available
This appears to be fixed. -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 425043] Re: package quickly 0.2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Last time I tested with the latest updates in karmic it seems to be fixed. -- package quickly 0.2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/425043 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.com/mailman/listinfo/ubuntu-bugs
[Bug 434043] Re: euca-run-instances emi-xxxxxxxx -k key doesn't start an instance
** Also affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- euca-run-instances emi- -k key doesn't start an instance https://bugs.launchpad.net/bugs/434043 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 434036] Re: euca-describe-availability-zones verbose doesn't report the types of instances available
** Also affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- 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 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 434043] Re: euca-run-instances emi-xxxxxxxx -k key doesn't start an instance
** Also affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- euca-run-instances emi- -k key doesn't start an instance https://bugs.launchpad.net/bugs/434043 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.com/mailman/listinfo/ubuntu-bugs
[Bug 434036] Re: euca-describe-availability-zones verbose doesn't report the types of instances available
** Also affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 423391] Re: release.py crashed with HTTPError in exchange_request_token_for_access_token()
I think you fixed it. It updates fine now. Thanks -- release.py crashed with HTTPError in exchange_request_token_for_access_token() https://bugs.launchpad.net/bugs/423391 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.com/mailman/listinfo/ubuntu-bugs
[Bug 425653] Re: midori assert failure: midori: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed.
** Attachment added: CoreDump.gz http://launchpadlibrarian.net/31437015/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/31437016/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/31437017/Disassembly.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/31437018/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/31437019/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/31437020/Registers.txt ** Attachment added: Stacktrace.txt http://launchpadlibrarian.net/31437021/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/31437022/ThreadStacktrace.txt ** Visibility changed to: Public -- midori assert failure: midori: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed. https://bugs.launchpad.net/bugs/425653 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.com/mailman/listinfo/ubuntu-bugs
[Bug 425043] [NEW] package quickly 0.2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Binary package hint: quickly Description:Ubuntu karmic (development branch) Release:9.10 apt-cache policy quickly quickly: Installed: 0.2.2 Candidate: 0.2.2 Version table: *** 0.2.2 0 500 http://ubuntu.osuosl.org karmic/universe Packages 100 /var/lib/dpkg/status ProblemType: Package Architecture: amd64 Date: Fri Sep 4 16:31:18 2009 DistroRelease: Ubuntu 9.10 ErrorMessage: subprocess installed post-installation script returned error exit status 1 Package: quickly 0.2.2 PackageArchitecture: all ProcVersionSignature: Ubuntu 2.6.31-9.29-generic SourcePackage: quickly Title: package quickly 0.2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Uname: Linux 2.6.31-9-generic x86_64 ** Affects: quickly (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package -- package quickly 0.2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/425043 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.com/mailman/listinfo/ubuntu-bugs
[Bug 425043] Re: package quickly 0.2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Attachment added: AptOrdering.txt http://launchpadlibrarian.net/31380392/AptOrdering.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/31380393/Dependencies.txt ** Attachment added: Dmesg.txt http://launchpadlibrarian.net/31380394/Dmesg.txt ** Attachment added: DpkgTerminalLog.gz http://launchpadlibrarian.net/31380395/DpkgTerminalLog.gz -- package quickly 0.2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/425043 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.com/mailman/listinfo/ubuntu-bugs
