[Bug 813400] Re: lxc-create -t ubuntu complains about /dev/pts
** Changed in: apt (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/813400 Title: lxc-create -t ubuntu complains about /dev/pts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/813400/+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 851611] Re: Oneiric: Upgrade to 2.0.1+bzr1256 blocks
The error seems to have been transient. I killed the hanging eucalyptus postinst process and I got no further hang. -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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 851611] Re: Oneiric: Upgrade to 2.0.1+bzr1256 blocks
I just updated and still have a hanging wget: ... Setting up kdepim-runtime (4:4.7.1-0ubuntu3) ... Setting up libcouchdb-glib-1.0-2 (0.7.4-0ubuntu2) ... Setting up libdesktopcouch-glib-1.0-2 (0.7.4-0ubuntu2) ... Setting up oneconf (0.2.6.4) ... Setting up software-center (4.1.23.4) ... Updating software catalog...this may take a moment. Software catalog update was successful. Setting up eucalyptus-admin-tools (2.0.1+bzr1256-0ubuntu8) ... Setting up eucalyptus-common (2.0.1+bzr1256-0ubuntu8) ... eucalyptus start/running, process 8050 $ ps aux | grep wget root 8873 0.0 0.0 27720 2304 ?S08:29 0:00 wget -q -T10 -t1 -O- --no-check-certificate https://192.168.1.122:8443/register spindler 10716 0.0 0.0 12040 900 pts/2S+ 10:00 0:00 grep --color=auto wget -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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 851611] Re: Oneiric: Upgrade to 2.0.1+bzr1256 blocks
Unfortunately killing the wget in a loop is now not continuing the eucalyptus start job. Also calling 'sudo stop eucalyptus' failed to change anything, the eucalyptus start job is hanging. -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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 851611] [NEW] Oneiric: Upgrade to 2.0.1+bzr1256 blocks
Public bug reported: Today's upgrade to eucalyptus blocks on my system: Setting up unity-lens-applications (0.4.6-0ubuntu1) ... Setting up unity-lens-files (0.6.6-0ubuntu1) ... Setting up compiz-fusion-plugins-main (1:0.9.5.94+bzr20110915-0ubuntu1) ... Setting up eucalyptus-admin-tools (2.0.1+bzr1256-0ubuntu7) ... Setting up eucalyptus-common (2.0.1+bzr1256-0ubuntu7) ... eucalyptus start/running, process 17255 hang Further eucalyptus cannot be stopped via the upstart job: $ sudo stop eucalyptus hang The usual log files are being written too and in cloud-debug.log I see several connection refused messages, maybe because the node controller is currently not up: 08:26:05 DEBUG [ChannelUtil:New I/O client boss #2] java.net.ConnectException: Connection refused java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592) at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:351) ... --- .etc.eucalyptus.eucalyptus.cc.conf: CC_NAME=Weberstrasse ApportVersion: 1.23-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 11.10 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) NonfreeKernelModules: nvidia Package: eucalyptus (not installed) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Tags: oneiric running-unity Uname: Linux 3.0.0-11-generic x86_64 UpgradeStatus: Upgraded to oneiric on 2011-09-12 (3 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected oneiric running-unity ** Tags added: apport-collected oneiric running-unity ** Description changed: Today's upgrade to eucalyptus blocks on my system: Setting up unity-lens-applications (0.4.6-0ubuntu1) ... Setting up unity-lens-files (0.6.6-0ubuntu1) ... Setting up compiz-fusion-plugins-main (1:0.9.5.94+bzr20110915-0ubuntu1) ... Setting up eucalyptus-admin-tools (2.0.1+bzr1256-0ubuntu7) ... Setting up eucalyptus-common (2.0.1+bzr1256-0ubuntu7) ... eucalyptus start/running, process 17255 hang Further eucalyptus cannot be stopped via the upstart job: $ sudo stop eucalyptus hang The usual log files are being written too and in cloud-debug.log I see several connection refused messages, maybe because the node controller is currently not up: 08:26:05 DEBUG [ChannelUtil:New I/O client boss #2] java.net.ConnectException: Connection refused java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592) at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:351) ... + --- + .etc.eucalyptus.eucalyptus.cc.conf: CC_NAME=Weberstrasse + ApportVersion: 1.23-0ubuntu1 + Architecture: amd64 + DistroRelease: Ubuntu 11.10 + InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) + NonfreeKernelModules: nvidia + Package: eucalyptus (not installed) + ProcEnviron: + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 + Tags: oneiric running-unity + Uname: Linux 3.0.0-11-generic x86_64 + UpgradeStatus: Upgraded to oneiric on 2011-09-12 (3 days ago) + UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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 851611] EucalyptusCCLog.gz
apport information ** Attachment added: EucalyptusCCLog.gz https://bugs.launchpad.net/bugs/851611/+attachment/2411458/+files/EucalyptusCCLog.gz -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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 851611] EucalyptusCloudOutputLog.gz
apport information ** Attachment added: EucalyptusCloudOutputLog.gz https://bugs.launchpad.net/bugs/851611/+attachment/2411460/+files/EucalyptusCloudOutputLog.gz -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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 851611] EucalyptusCloudDebugLog.gz
apport information ** Attachment added: EucalyptusCloudDebugLog.gz https://bugs.launchpad.net/bugs/851611/+attachment/2411459/+files/EucalyptusCloudDebugLog.gz -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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 851611] EucalyptusAxis2cLog.gz
apport information ** Attachment added: EucalyptusAxis2cLog.gz https://bugs.launchpad.net/bugs/851611/+attachment/2411457/+files/EucalyptusAxis2cLog.gz -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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 851611] eucalyptus.local.conf.txt
apport information ** Attachment added: eucalyptus.local.conf.txt https://bugs.launchpad.net/bugs/851611/+attachment/2411464/+files/eucalyptus.local.conf.txt -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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 851611] EucalyptusHTTPDErrorLog.gz
apport information ** Attachment added: EucalyptusHTTPDErrorLog.gz https://bugs.launchpad.net/bugs/851611/+attachment/2411461/+files/EucalyptusHTTPDErrorLog.gz -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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 851611] eucalyptus.conf.txt
apport information ** Attachment added: eucalyptus.conf.txt https://bugs.launchpad.net/bugs/851611/+attachment/2411463/+files/eucalyptus.conf.txt -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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 851611] EucalyptusInstalledVersions.txt
apport information ** Attachment added: EucalyptusInstalledVersions.txt https://bugs.launchpad.net/bugs/851611/+attachment/2411462/+files/EucalyptusInstalledVersions.txt -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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
Re: [Bug 851611] Re: Oneiric: Upgrade to 2.0.1+bzr1256 blocks
I confirm James finding, I have the wget running as well. -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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 851611] Re: Oneiric: Upgrade to 2.0.1+bzr1256 blocks
For the record, I killed the post instll script 'eucalyptus- common.postinst', leaving eucalyptus unconfigured to proceed working on the system. -- 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/851611 Title: Oneiric: Upgrade to 2.0.1+bzr1256 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/851611/+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 765275] Re: metadata server cannot be contacted when deploying new instances on EUC
We tried the following to overcome the problem, nothing was successful: 1) Restart eucalyptus-cc 2) Reboot front-end and node-controlle 3) Purge and reinstall eucalyptus-cc -- 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/765275 Title: metadata server cannot be contacted when deploying new instances on EUC -- 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
Re: [Bug 757258] [NEW] Unable to reach instances from their public IP address
Did you enable the accessibility of the instance ports via euca-authorize? What is the output of euca-describe-groups for the clouds admin user? -- 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/757258 Title: Unable to reach instances from their public IP address -- 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 728018] Re: 10.04 LTS: Failure to start instance due to network address failure
The only work around for the problem seems to be to terminate instances and then try again. -- 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/728018 Title: 10.04 LTS: Failure to start instance due to network address failure -- 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 728018] Re: 10.04 LTS: Failure to start instance due to network address failure
I wonder if the timeout for the termination request leads to a situation when the pool of network addresses gets empty. Is there a way to see the internal IP address allocation? -- 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/728018 Title: 10.04 LTS: Failure to start instance due to network address failure -- 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 728018] Re: 10.04 LTS: Failure to start instance due to network address failure
The problem seems to occur quite randomly, here the statistics from the last 5 test runs: Started: 25 Clients, 4 Servers. Stopped: 21 Started: 340 Clients, 27 Servers. Stopped: 360 Started: 70 Clients, 8 Servers. Stopped: 71 Started: 70 Clients, 5 Servers. Stopped: 68 Started: 30 Clients, 6 Servers. Stopped: 26 -- 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/728018 Title: 10.04 LTS: Failure to start instance due to network address failure -- 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 728018] Re: 10.04 LTS: Failure to start instance due to network address failure
From time to time I see these timeouts, could they be related? 4 0 8 path=/services/Eucalyptus/?AWSAccessKeyId=WKy3rMzOWPouVOxK1p3Ar1C2uRBwa2FBXnCwA ction=TerminateInstancesInstanceId.1=i-47F10968InstanceId.2=i-4D930877Instanc eId.3=i-2BFF05A8InstanceId.4=i-48E108C9InstanceId.5=i-51070907SignatureMethod =HmacSHA256SignatureVersion=2Timestamp=2011-03-04T14%3A08%3A28Version=2009-11 -30Signature=8N3z8cgovnd94xj2WuFwyDdoF9DohA5hYqe%2ByREbBsE%3D Failure: 408 Request Timeout -- 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/728018 Title: 10.04 LTS: Failure to start instance due to network address failure -- 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 728018] Re: 10.04 LTS: Failure to start instance due to network address failure
And another one: [Thu Mar 3 11:48:55 2011][011912][EUCADEBUG ] RunInstances(): running instance i-3393055A with emiId emi-0CE515A7... [Thu Mar 3 11:48:55 2011][011912][EUCAERROR ] vnetAddHost(): failed to add host d0:0d:33:93:05:5A on vlan 10 [Thu Mar 3 11:48:55 2011][011912][EUCADEBUG ] RunInstances(): assigning MAC/IP: d0:0d:33:93:05:5A/0.0.0.0/0.0.0.0/16 [Thu Mar 3 11:48:55 2011][011912][EUCAERROR ] RunInstances(): could not find/initialize any free network address, failing doRunInstances() [Thu Mar 3 11:48:55 2011][011912][EUCADEBUG ] RunInstances(): done [Thu Mar 3 11:48:55 2011][011912][EUCAERROR ] vnetAttachTunnels(): bad input params [Thu Mar 3 11:48:55 2011][011912][EUCADEBUG ] maintainNetworkState(): failed to attach tunnels for vlan 10 during maintainNetworkState() [Thu Mar 3 11:48:55 2011][011912][EUCAERROR ] shawn(): network state maintaina Is there any more meaningful debug information I can provide than the excerpts from the cc.log? -- 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/728018 Title: 10.04 LTS: Failure to start instance due to network address failure -- 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 728018] [NEW] 10.04 LTS: Failure to start instance due to network address failure
Public bug reported: I'm running tests and launch rather large numbers of instances on a UEC running with Ubuntu 10.04 LTS. I discovered that instances regularly fail to start and it seems to be that they never get a network address assigned. In the cc.log I discovered the following entries: [Wed Mar 2 19:34:08 2011][011910][EUCADEBUG ] RunInstances(): running instance i-3D9C0776 with emiId emi-0CE515A7... [Wed Mar 2 19:34:08 2011][011910][EUCAERROR ] vnetAddHost(): failed to add host d0:0d:3D:9C:07:76 on vlan 10 [Wed Mar 2 19:34:08 2011][011910][EUCADEBUG ] RunInstances(): assigning MAC/IP: d0:0d:3D:9C:07:76/0.0.0.0/0.0.0.0/14 [Wed Mar 2 19:34:08 2011][011910][EUCAERROR ] RunInstances(): could not find/initialize any free network address, failing doRunInstances() The problems seems to be only temporary, as later on I can launch more instances. Eucalyptus in use is 1.6.2-0ubuntu30.4. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- 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/728018 Title: 10.04 LTS: Failure to start instance due to network address failure -- 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 728018] Re: 10.04 LTS: Failure to start instance due to network address failure
Another fail during tonight's test run: [Thu Mar 3 01:36:43 2011][011910][EUCADEBUG ] RunInstances(): running instance i-49AF07C3 with emiId emi-0CE515A7... [Thu Mar 3 01:36:43 2011][011910][EUCAERROR ] vnetAddHost(): failed to add host d0:0d:49:AF:07:C3 on vlan 10 [Thu Mar 3 01:36:43 2011][011910][EUCADEBUG ] RunInstances(): assigning MAC/IP: d0:0d:49:AF:07:C3/0.0.0.0/0.0.0.0/6 [Thu Mar 3 01:36:43 2011][011910][EUCAERROR ] RunInstances(): could not find/initialize any free network address, failing doRunInstances() [Thu Mar 3 01:36:43 2011][011910][EUCADEBUG ] RunInstances(): done [Thu Mar 3 01:36:43 2011][011910][EUCAERROR ] vnetAttachTunnels(): bad input params [Thu Mar 3 01:36:43 2011][011910][EUCADEBUG ] maintainNetworkState(): failed to attach tunnels for vlan 10 during maintainNetworkState() [Thu Mar 3 01:36:43 2011][011910][EUCAERROR ] shawn(): network state maintainance failed [Thu Mar 3 01:36:45 2011][012497][EUCADEBUG ] monitor_thread(): running [Thu Mar 3 01:36:45 2011][012497][EUCAINFO ] refresh_resources(): called [Thu Mar 3 01:36:45 2011][012497][EUCADEBUG ] refresh_resources(): calling http://172.24.55.254:8775/axis2/services/EucalyptusNC [Thu Mar 3 01:36:45 2011][012497][EUCADEBUG ] refresh_resources(): time left for next op: 60 -- 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/728018 Title: 10.04 LTS: Failure to start instance due to network address failure -- 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 728018] Re: 10.04 LTS: Failure to start instance due to network address failure
For completeness the network definition of the cloud. If wanted I can grant ssh access to the system: VNET_MODE=MANAGED-NOVLAN VNET_SUBNET=172.19.0.0 VNET_NETMASK=255.255.0.0 VNET_DNS=172.24.1.1 VNET_ADDRSPERNET=32 VNET_PUBLICIPS=172.24.129.136 Again, when starting new instances it works and the error does not show up again. -- 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/728018 Title: 10.04 LTS: Failure to start instance due to network address failure -- 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 690142] Re: euca-describe-storage-controllers missing module
The problem exists on the Ubuntu 10.10 training cloud as well. Maybe a packaging error? ** Changed in: eucalyptus (Ubuntu) Status: New = Confirmed -- 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/690142 Title: euca-describe-storage-controllers missing module -- 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 667841] [NEW] some virtual machines hang upon boot with maverick kernel on lucid host
Public bug reported: Binary package hint: kvm I've updated my kernel on an Ubuntu 10.04 host with linux-image-generic- pae-lts-backport-maverick. Since then two virtual machines using Lucid do no longer start. The boot hangs with an empty screen and a _ displayed on the top left. When I reboot the machine to the original Lucid kernel, the virtual machines will boot. ** Affects: kvm (Ubuntu) Importance: Undecided Status: New -- some virtual machines hang upon boot with maverick kernel on lucid host https://bugs.launchpad.net/bugs/667841 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to 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 666836] [NEW] [10.04] Deleting security groups of a user
Public bug reported: The default security group of a user can not be deleted with admin privileges. E.g. $ euca-describe-groups | grep davidchen GROUP davidchen default default group PERMISSION davidchen default ALLOWS tcp 22 22 FROM CIDR 0.0.0.0/0 There is no unique name for the (deleted) user davidchen's default group. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Deleting security groups of a user + [10.04] Deleting security groups of a user -- [10.04] Deleting security groups of a user https://bugs.launchpad.net/bugs/666836 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 660055] Re: [10.04] instances gets public ip address after disassociate-address
** Summary changed: - instances gets public ip address after disassociate-address + [10.04] instances gets public ip address after disassociate-address -- [10.04] instances gets public ip address after disassociate-address https://bugs.launchpad.net/bugs/660055 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 660055] [NEW] instances gets public ip address after disassociate-address
Public bug reported: When I start an instance with --addressing-private option, associate an elastic IP to it and take this away later, the instance claims another public ip instead of staying private. $ euca-describe-instances RESERVATION r-3B69071E spindlerdefault INSTANCEi-436507FB emi-87F617CA172.19.2.2 172.19.2.2 pending spindler0 m1.small 2010-10-13T16:55:38.976Z classcloud eki-EDF71CF2 $ euca-allocate-address ADDRESS 172.24.129.128 $ euca-associate-address 172.24.129.128 -i i-436507FB ADDRESS 172.24.129.128 i-436507FB $ euca-describe-instances i-436507FB RESERVATION r-3B69071E spindlerdefault INSTANCEi-436507FB emi-87F617CA172.24.129.128 172.19.2.2 running spindler0 m1.small 2010-10-13T16:55:38.976Z classcloud eki-EDF71CF2 $ euca-disassociate-address 172.24.129.128 ADDRESS 172.24.129.128 $ euca-describe-instances RESERVATION r-3B69071E spindlerdefault INSTANCEi-436507FB emi-87F617CA172.24.129.139 172.19.2.2 running spindler0 m1.small 2010-10-13T16:55:38.976Z classcloud eki-EDF71CF2 ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- instances gets public ip address after disassociate-address https://bugs.launchpad.net/bugs/660055 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
Re: [Bug 660055] Re: instances gets public ip address after disassociate-address
It's Eucalyptus 1.6.2 on Ubuntu 10.04.1. -- instances gets public ip address after disassociate-address https://bugs.launchpad.net/bugs/660055 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 590929] Re: eucalyptus create and delete volumes sometimes fail on lvm commands (POC + ENT configs)
I can reproduce the problem on the training cloud: $ for i in `seq 1 100`; do euca-create-volume -z TorstenCloud -s1; done ... VOLUME vol-52B905E31 creating2010-09-02T06:27:50.814Z VOLUME vol-5F2906521 creating2010-09-02T06:27:51.142Z VOLUME vol-598F062A1 creating2010-09-02T06:27:51.487Z Volume: Error while communicating with Storage Controller: CreateStorageVolume:I nternal Error. Volume: Error while communicating with Storage Controller: CreateStorageVolume:I nternal Error. Volume: Error while communicating with Storage Controller: CreateStorageVolume:I nternal Error. ... $ euca-describe-volumes | grep failed VOLUME vol-52B905E3 1 TorstenCloudfailed 2010-09-02T06:27:50.814Z $ euca-describe-volumes | grep unavailable | wc -l 13 $ euca-describe-volumes | grep available | grep -v unavailable | wc -l 48 I'll add ppa:ubuntu-virt/ppa to the sources.list and report what happens when re-running the test. -- eucalyptus create and delete volumes sometimes fail on lvm commands (POC + ENT configs) https://bugs.launchpad.net/bugs/590929 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 517086] Re: euca-create-volume fails at times with Error communicating with Storage Controller
Here we go, the problem is fixed: $ for i in $(seq 1 32); do euca-create-volume -s 1 -z TorstenCloud; done $ euca-describe-volumes | grep avail | wc -l 30 $ euca-describe-volumes | grep creat | wc -l 0 $ euca-describe-volumes | grep fail | wc -l 2 $ for i in $(euca-describe-volumes | cut -c8-20 | xargs); do euca- delete-volume $i; done $ for i in $(seq 1 32); do euca-create-volume -s 1 -z TorstenCloud; done $ euca-describe-volumes | grep avail | wc -l 32 $ for i in $(euca-describe-volumes | cut -c8-20 | xargs); do euca- delete-volume $i; done $ for i in $(seq 1 32); do euca-create-volume -s 1 -z TorstenCloud; done $ euca-describe-volumes | grep avail | wc -l 32 $ for i in $(euca-describe-volumes | cut -c8-20 | xargs); do euca- delete-volume $i; done $ for i in $(seq 1 32); do euca-create-volume -s 1 -z TorstenCloud; done $ euca-describe-volumes | grep avail | wc -l 32 -- euca-create-volume fails at times with Error communicating with Storage Controller https://bugs.launchpad.net/bugs/517086 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
Re: [Bug 517086] Re: euca-create-volume fails at times with Error communicating with Storage Controller
@Carlos, the cloud of the error reports is long gone. If need be I can try to recreate the problem on a new one next week. -- euca-create-volume fails at times with Error communicating with Storage Controller https://bugs.launchpad.net/bugs/517086 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
Re: [Bug 598182] [NEW] eucalyptus-cc and uec-component-listener services are not started
Is the cluster registered in the cloud at all? Do you see it with euca-describe-availability-zones? -- eucalyptus-cc and uec-component-listener services are not started https://bugs.launchpad.net/bugs/598182 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
Re: [Bug 592648] Re: Not all keys present
I created a new cloud and this time via packaged install and this time the keys were present after registering the cluster controller. Please close this bug as it cannot be reproduced. -- Not all keys present https://bugs.launchpad.net/bugs/592648 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
Re: [Bug 592648] Re: Not all keys present
Nope, I didn't do that before hand. I copied it after it failed. But it seems it's then to late already. I still don't quite understand how the keys can be missing - I thought they are setup when registering a cluster. I also believe this is where it went wrong. -- Not all keys present https://bugs.launchpad.net/bugs/592648 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 592648] [NEW] Not all keys present
Public bug reported: I've created a new cloud using the install from packages method. The first unusual thing was that the CC was not automatically registered, even when running on the same host as the CLC. Now the next problem manifests in the node not being registered due to missing keys: $ sudo euca_conf --register-nodes pulasan.vmcp INFO: We expect all nodes to have eucalyptus installed in //var/lib/eucalyptus/keys for key synchronization. Warning: cannot file file node-cert.pem in //var/lib/eucalyptus/keys/ Warning: cannot file file cluster-cert.pem in //var/lib/eucalyptus/keys/ Warning: cannot file file node-pk.pem in //var/lib/eucalyptus/keys/ Trying rsync to sync keys with pulasan.vmcp...eucalyp...@pulasan.vmcp's password: done. $ sudo ls /var/lib/eucalyptus/keys cloud-cert.pem euca.p12 nc-client-policy.xml TorstenTest ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- Not all keys present https://bugs.launchpad.net/bugs/592648 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 572388] Re: NC not available when auto registrating with second cloud present
The first existing cloud was using the simple topology: one front-end, one node controller. The cloud we installed first was made up of 3 machines: 1 CLC+Walrus, 1 CC+SC, 2 NC. After installing the second cloud, both clouds had two clusters registered against it. However, the output of euca-describe- availability-zones verbose showed that the nodes were not registered correctly against the CC of the second cloud. So we could never start an instance in the second cloud. -- NC not available when auto registrating with second cloud present https://bugs.launchpad.net/bugs/572388 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
Re: [Bug 577027] [NEW] unable to ssh to guest vm after volume attach
On Fri, 2010-05-07 at 14:35 +, Jason Rogers wrote: ... I had a guest vm running on a eucalyptus cloud using virtio for disk and network I/O. I also had an ssh session on the guest vm. When I attach a volume to the instance using euca-attach-volume I lose network connectivity to the guest. With what arguments did you call euca-attach-volume? I believe there is a problem when specifying /dev/sda instead of /dev/sdb. -- unable to ssh to guest vm after volume attach https://bugs.launchpad.net/bugs/577027 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 574366] [NEW] private ip address assigned twice
Public bug reported: The 172.19.1.2 IP address was assigned twice in this cloud: $ euca-describe-instances RESERVATION r-4AAA0905 admin default INSTANCEi-42F507EC emi-6E2F1366172.19.1.2 172.19.1.2 running admin 0 m1.small2010-05-03T10:41:12.233Z torsten eki-9F361879 RESERVATION r-4B3E0958 admin default INSTANCEi-3F3C06BB emi-6E2F1366172.19.1.3 172.19.1.3 running admin 0 m1.small1970-01-01T00:00:00.284Z torsten eki-9F361879 RESERVATION r-49A007E7 admin default INSTANCEi-4847087F emi-6E2F1366172.19.1.2 172.19.1.2 running admin 0 m1.small1970-01-01T00:00:00.283Z torsten eki-9F361879 ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- private ip address assigned twice https://bugs.launchpad.net/bugs/574366 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 574366] Re: private ip address assigned twice
This seems to have happened while dnsmasq was running on an instance - the instance got the ip from itself. After disabling dhcp for dnsmasq on another trial instance, the problem could no longer be reproduced. -- private ip address assigned twice https://bugs.launchpad.net/bugs/574366 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 572388] [NEW] NC not available when auto registrating with second cloud present
Public bug reported: One cloud is already running. When installing a new cloud in the same subnet, auto registration of nodes to the second cloud does not seem to work. From the CLC registration.log: 2010-04-30 10:41:13-04:00 | 3882 - Calling node rockstars-cluster node 10.153.108.113 2010-04-30 10:41:18-04:00 | 3882 - euca_conf --register-nodes returned 0 Output of $ euca-describe-availability-zones verbose AVAILABILITYZONErockstars-cluster 10.153.108.210 AVAILABILITYZONE|- vm types free / max cpu ram disk AVAILABILITYZONE|- m1.small / 1192 2 AVAILABILITYZONE|- c1.medium / 1256 5 AVAILABILITYZONE|- m1.large / 251210 AVAILABILITYZONE|- m1.xlarge / 2 102420 AVAILABILITYZONE|- c1.xlarge / 4 204820 eucalyp...@rockstars-clc:~$ ssh 10.153.108.113 succeeds. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- NC not available when auto registrating with second cloud present https://bugs.launchpad.net/bugs/572388 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 572388] Re: NC not available when auto registrating with second cloud present
After stopping the other cloud and reinstalling it worked. -- NC not available when auto registrating with second cloud present https://bugs.launchpad.net/bugs/572388 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
Re: [Bug 546997] [NEW] qemu-kvm-0.12.3+noroms-0ubuntu2: qemu-nbd: error while reading
Does it work without the -P 1 option? -- qemu-kvm-0.12.3+noroms-0ubuntu2: qemu-nbd: error while reading https://bugs.launchpad.net/bugs/546997 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 517086] Re: euca-create-volume fails at times with Error communicating with Storage Controller
On Lucid, I don't get the Volume: Error communicating with Storage Controller: CreateStorageVolume:Internal Error. error anymore. However, not all volume groups are deleted: $ sudo lvscan ACTIVE'/dev/vg-wsdyiQ../lv-K0hXfA..' [1.00 GiB] inherit $ sudo vgscan Reading all physical volumes. This may take a while... Found volume group vg-wsdyiQ.. using metadata type lvm2 Note that at times a volume is stuck in the 'creating' stage. It can be deleted via euca-delete-volume, but deletion does not seem to be complete. The situation seems to get worse when doing the create/delete volume more often: $ for i in $(seq 1 32); do euca-create-volume -s 1 -z torsten; done $ euca-describe-volumes | grep avail | wc -l 29 $ euca-describe-volumes | grep creat | wc -l 3 $ for i in $(euca-describe-volumes | cut -c8-20 | xargs); do euca-delete-volume $i; done $ for i in $(seq 1 32); do euca-create-volume -s 1 -z torsten; done $ euca-describe-volumes | grep avail | wc -l 26 $ euca-describe-volumes | grep creat | wc -l 6 $ for i in $(euca-describe-volumes | cut -c8-20 | xargs); do euca-delete-volume $i; done $ for i in $(seq 1 32); do euca-create-volume -s 1 -z torsten; done $ euca-describe-volumes | grep avail | wc -l 24 $ euca-describe-volumes | grep creat | wc -l 8 $ for i in $(euca-describe-volumes | cut -c8-20 | xargs); do euca-delete-volume $i; done -- euca-create-volume fails at times with Error communicating with Storage Controller https://bugs.launchpad.net/bugs/517086 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
Re: [Bug 470355] Re: ec2-bundle-vol and ec2-upload-bundle result in non accepted manifest
On Wed, 2010-03-17 at 13:32 +, Jean-Pierre Dion wrote: ... 2) euca-upload-bundle -b kernel_bucket -m /tmp/vmlinuz-2.6.31-14-server.manifest.xml ... 3) euca-register kernel_buckets/vmlinuz-2.6.31-14-server.manifest.xml Just to make sure that there is no typing mistake: the euca-register should say euca-register kernel_bucket/vmlinuz-2.6.31-14-server.manifest.xml -- ec2-bundle-vol and ec2-upload-bundle result in non accepted manifest https://bugs.launchpad.net/bugs/470355 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
Re: [Bug 513273] Re: kvm with -vga std is broken since karmic
The bios files are missing from the package, instead there is still a link pointing nowhere: lrwxrwxrwx 1 root root 22 2010-03-05 08:26 vgabios.bin - ../vgabios/vgabios.bin lrwxrwxrwx 1 root root 29 2010-03-05 08:26 vgabios-cirrus.bin - ../vgabios/vgabios.cirrus.bin When the two links are removed from debian/links the new BIOS are placed in /usr/share/qemu. Attached is a debdiff for the change. ** Patch added: qemu-kvm.links.debdiff http://launchpadlibrarian.net/40231660/qemu-kvm.links.debdiff -- kvm with -vga std is broken since karmic https://bugs.launchpad.net/bugs/513273 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 513273] Re: kvm with -vga std is broken since karmic
I just tried 0.12.3-0ubuntu5~ppa2 and I don't get any errors when launching $ kvm -vga std -hda ./lucid.qcow2 -- kvm with -vga std is broken since karmic https://bugs.launchpad.net/bugs/513273 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 531741] Re: driver cache='none'/ disappears after adding
The bug also exists in Lucid, libvirt 0.7.5-5ubuntu9. -- driver cache='none'/ disappears after adding https://bugs.launchpad.net/bugs/531741 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 531455] Re: daily server ISO install fails with a kernel OOPS in KVM
I tried to reproduce your kernel oops problem with the lucid alpha 3 server CD, but no kernel oops was given. Can you reproduce the error on a different hardware? -- daily server ISO install fails with a kernel OOPS in KVM https://bugs.launchpad.net/bugs/531455 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
Re: [Bug 531455] Re: daily server ISO install fails with a kernel OOPS in KVM
*** This bug is a duplicate of bug 531823 *** https://bugs.launchpad.net/bugs/531823 It's a 32bit system, maybe that's the key difference? a) uname -a spind...@spitfire:~/t$ uname -a Linux spitfire 2.6.32-15-generic #22-Ubuntu SMP Tue Mar 2 02:24:17 UTC 2010 i686 GNU/Linux b) cat /proc/cpuinfo $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz stepping: 10 cpu MHz : 800.000 cache size : 3072 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida tpr_shadow vnmi flexpriority bogomips: 5054.00 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz stepping: 10 cpu MHz : 2531.000 cache size : 3072 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida tpr_shadow vnmi flexpriority bogomips: 5053.95 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: -- daily server ISO install fails with a kernel OOPS in KVM https://bugs.launchpad.net/bugs/531455 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 530091] Re: [alpha3] NC fails to be detected.
After reinstallation nothing changes. I removed quiet and splash from the kernel boot command line and see the following report: init: eucalyptus-network (lo) main process (704) killed by TERM signal -- [alpha3] NC fails to be detected. https://bugs.launchpad.net/bugs/530091 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
Re: [Bug 530091] Re: [alpha3] NC fails to be detected.
On Wed, 2010-03-03 at 09:48 +, Thierry Carrez wrote: Looking at the authorized_keys, might be a node re-registration issue. Did you register the same Node IP with the CC in the past ? Yes, it was registered before. When you deregistered/registered manually the node, did you get any error ? Nope. But when I register the node it is not listed anywhere, e.g. $ sudo euca_conf --register-nodes 192.168.1.106 INFO: We expect all nodes to have eucalyptus installed in //var/lib/eucalyptus/keys for key synchronization. Trying rsync to sync keys with 192.168.1.106...The authenticity of host '192.168.1.106 (192.168.1.106)' can't be established. RSA key fingerprint is 5e:3f:83:e2:83:18:c5:f9:04:3f:a1:f2:9a:94:30:4e. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.1.106' (RSA) to the list of known hosts. eucalyp...@192.168.1.106's password: done. ubu...@frontend:/etc/eucalyptus$ grep -ri 106 * grep: preseed/preseed.conf: Permission denied After deregister, what do you have in /var/lib/eucalyptus/nodes.list ? sudo euca_conf --deregister-nodes 192.168.1.106 [sudo] password for ubuntu: SUCCESS: removed node '192.168.1.106' ubu...@frontend:~$ cd /etc/eucalyptus/ ubu...@frontend:/etc/eucalyptus$ grep 106 * eucalyptus.conf:NODES=192.168.1.106 I added it manually to eucalyptus.conf in the past, will remove it. Could you reproduce on a full new setup (reinstall the CC)? (I can't) I will do so, first reinstall the CC, then the NC and report back if the situation changes. The process is: 0/ NC Installer copies CC key to NC authorized_keys 1/ NC publishes its existence 2/ CC picks up the publication 3/ CC runs euca_conf --register-nodes 4/ euca_conf --register-nodes syncs up the eucalyptus CC keys to the NC /var/lib/eucalyptus/keys 5/ euca_conf --register-nodes adds IP to the CC nodes.list 6/ NC picks up keys and starts up, starts writing up messages to nc.log From your logs it looks like 0-3 is working alright, and that 6 never happens. Could you tell where it stops ? ** Changed in: eucalyptus (Ubuntu) Importance: High = Medium ** Changed in: eucalyptus (Ubuntu) Status: Confirmed = Incomplete -- [alpha3] NC fails to be detected. https://bugs.launchpad.net/bugs/530091 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 530091] Re: [alpha3] NC fails to be detected.
On a fresh install of front-end and node controller the cloud works as expected: ubu...@frontend:/var/log/eucalyptus$ euca-describe-availability-zones verbose AVAILABILITYZONEtorsten 192.168.1.103 AVAILABILITYZONE|- vm types free / max cpu ram disk AVAILABILITYZONE|- m1.small 0002 / 0002 1128 2 AVAILABILITYZONE|- c1.medium0002 / 0002 1256 5 AVAILABILITYZONE|- m1.large 0001 / 0001 251210 AVAILABILITYZONE|- m1.xlarge0001 / 0001 2 102420 AVAILABILITYZONE|- c1.xlarge / 4 204820 -- [alpha3] NC fails to be detected. https://bugs.launchpad.net/bugs/530091 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
Re: [Bug 519648] Re: After all-in-one setup node-cert.pem and node-pk.pem not found
Having the option to host a complete UEC on one machine is also relevant for training. Right now we fall back to one UEC per classroom due to the two machine requirement, or at most students working in pairs. -- After all-in-one setup node-cert.pem and node-pk.pem not found https://bugs.launchpad.net/bugs/519648 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 530091] Re: [alpha3] NC fails to be detected.
I'm pretty sure I waited for the front-end to be ready, e.g. euca- describe-availability-zones verbose returns a good output. I attach the registration log from the front-end. On the node the authorized_keys file contain a good key for the frontend. As user eucalyptus on the front-end I can do a password less login to node01 with ssh. I can re-install the node and see if it gets any better. $ sudo cat authorized_keys [sudo] password for ubuntu: ssh-rsa B3NzaC1yc2EBIwAAAQEAt9C17TNGYpqIyCT74LtzXE1fpVluKGCIql8HBufmux7a5/AdVqa+b4OMs+bkNbQRPJiaUmGKyRioHX9vZwngN8FlDxI35QG5keEd/flI0ltXghnOVBoHXh9QVc2ux78GzAu+u0bxI9En4DfETvidgTcVmHNSUJlT270oQX7JiXj0bfK87S/d5vzA4pZInODFYilX+RHCgaZocgYkYP2cGqH2hFR2KSmbzVgkeV0Axk9FQAMSmrrPwrnenYmC9oobo0LQ8ZUp/1STruQVxWkLph8wfPY0JRrw5PYmsYIf8hys9t5vqhNCKUs29tCJDaSy/HdcXYB/GwgFgSjkSaPE5Q== eucalyp...@frontend ssh-rsa B3NzaC1yc2EBIwAAAQEAt9C17TNGYpqIyCT74LtzXE1fpVluKGCIql8HBufmux7a5/AdVqa+b4OMs+bkNbQRPJiaUmGKyRioHX9vZwngN8FlDxI35QG5keEd/flI0ltXghnOVBoHXh9QVc2ux78GzAu+u0bxI9En4DfETvidgTcVmHNSUJlT270oQX7JiXj0bfK87S/d5vzA4pZInODFYilX+RHCgaZocgYkYP2cGqH2hFR2KSmbzVgkeV0Axk9FQAMSmrrPwrnenYmC9oobo0LQ8ZUp/1STruQVxWkLph8wfPY0JRrw5PYmsYIf8hys9t5vqhNCKUs29tCJDaSy/HdcXYB/GwgFgSjkSaPE5Q== eucalyp...@frontend ** Attachment added: registration.log http://launchpadlibrarian.net/39951028/registration.log -- [alpha3] NC fails to be detected. https://bugs.launchpad.net/bugs/530091 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
Re: [Bug 530091] Re: [alpha3] NC fails to be detected.
I tried the deregister and register but not change in the overall situation. For the logs on the node controller, I don't see nc.log: ubu...@node01:/var/log/eucalyptus$ ls axis2c.log euca_test_nc.log httpd-nc_error_log -- [alpha3] NC fails to be detected. https://bugs.launchpad.net/bugs/530091 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
Re: [Bug 530091] Re: [alpha3] NC fails to be detected.
Nothing of interest in there, I attach the two ** Attachment added: httpd-nc_error_log http://launchpadlibrarian.net/39962164/httpd-nc_error_log ** Attachment added: euca_test_nc.log http://launchpadlibrarian.net/39962165/euca_test_nc.log -- [alpha3] NC fails to be detected. https://bugs.launchpad.net/bugs/530091 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 530091] [NEW] [alpha3] NC fails to be detected.
Public bug reported: I installed a frontend and node with the alpha3 server CD. Frontend works fine, but $ euca-describe-availability-zones verbose does not have any node. I tried $ euca_conf --discover-nodes --no-rsync but the node was not discovered. I added it then by hand to /etc/eucalyptus/eucalyptus.conf and copied the keys manually. However, the node is still not part of the cloud. On the node I see the following eucalyptus processes: ubu...@node01:~$ ps aux | grep eucalyptus root 1211 0.0 0.0 4972 2176 ?Ss 15:52 0:00 apache2 -f /var/run/eucalyptus/httpd-nc.conf -D FOREGROUND 108 1260 0.0 0.0 45288 3988 ?Sl 15:52 0:00 apache2 -f /var/run/eucalyptus/httpd-nc.conf -D FOREGROUND root 1444 0.0 0.0 2232 1004 ?Ss 15:52 0:00 avahi-publish -s torstentest node _eucalyptus._tcp 8775 txtvers=1 protovers=1.5.0 type=node ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- [alpha3] NC fails to be detected. https://bugs.launchpad.net/bugs/530091 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 442598] Re: 'qemu-img snapshot' crashed, corrupting disk image
The following command did not give an error for me on Lucid Alpha 3, 2010-03-01 updates installed: $ qemu-img snapshot -c toast ./lucid.qcow2 Version: 0.12.3-0ubuntu2 Unfortunately I did not find a snapshot thereafter either. -- 'qemu-img snapshot' crashed, corrupting disk image https://bugs.launchpad.net/bugs/442598 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 426822] Re: qemu corrupts screen on resize
Cannot reproduce this problem with a Lucid alpha3 guest running on a Lucid alpha 3 host. qemu-kvm Version: 0.12.3-0ubuntu2 -- qemu corrupts screen on resize https://bugs.launchpad.net/bugs/426822 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 471446] Re: qemu segfaults with a -cpu option
This seems to be fixed on Lucid alpha 3: $ qemu -cpu pentium lucid.qcow2 kvm_run: Exec format error kvm_run returned -8 $ qemu -cpu 486 lucid.qcow2 kvm_run: Exec format error kvm_run returned -8 $ qemu -cpu pentium -no-kvm lucid.qcow2 (runs, slowly) -- qemu segfaults with a -cpu option https://bugs.launchpad.net/bugs/471446 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 513273] Re: kvm with -vga std give error and do not works
On Lucid Alpha3 I don't get console error messages, but a error: unknown command 'terminal'. unaligned pointer 0x8ecc0002 Aborted. Press any key to exit. -- kvm with -vga std give error and do not works https://bugs.launchpad.net/bugs/513273 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 512259] Re: lucid qemu: could not open disk image
I upgraded from Karmic to Lucid alpha 3 and cannot reproduce your problem. virsh start works fine for my old VMs. -- lucid qemu: could not open disk image https://bugs.launchpad.net/bugs/512259 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 453617] Re: kvm hangs at 100% cpu when connecting to forwarded ports
On Lucid alpha 3 an error is reported and kvm stops: $ sudo kvm -net nic -net user,hostfwd=tcp:127.0.0.1:-:80 -net user,hostfwd=tcp:127.0.0.1:-:22 -m 128 -smp 1 -drive file=disk0.qcow2kvm -net nic -net user,hostfwd=tcp:127.0.0.1:-:80 -net user,hostfwd=tcp:127.0.0.1:-:22 -m 128 -smp 1 -drive file=lucid.qcow2 could not set up host forwarding rule 'tcp:127.0.0.1:-:80' qemu-kvm Version: 0.12.3-0ubuntu2 -- kvm hangs at 100% cpu when connecting to forwarded ports https://bugs.launchpad.net/bugs/453617 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 450309] Re: assertion failure when using i82551 network card emulation
According to the original bug reporter this problem has been resolved in Lucid. -- assertion failure when using i82551 network card emulation https://bugs.launchpad.net/bugs/450309 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
Re: [Bug 503180] Re: [SRU] eucalyptus-cloud doesn't reply to requests (eucalyptus doesn't work after reboot or services restart issues due to upstart networking behavior)
I enabled karmic-proposed, installed eucalyptus-*-1.6~bzr931-0ubuntu7.5 on the training cloud in the datacenter. I rebooted node and frontend and the cloud was operational from the start. I started an instance and ssh'ed to it. All looks good and operational. -- [SRU] eucalyptus-cloud doesn't reply to requests (eucalyptus doesn't work after reboot or services restart issues due to upstart networking behavior) https://bugs.launchpad.net/bugs/503180 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 526506] [NEW] [karmic]: attaching volume to /dev/sda results in non operational node
Public bug reported: I made a mistake when trying to attach a volume to an instance and gave it device /dev/sda. Instead of failing gracefully the node stopped to operate. Here's the log: [Tue Feb 23 15:14:48 2010][001762][EUCAINFO ] started VM instance i-3B530725 [Tue Feb 23 15:18:13 2010][001762][EUCAINFO ] doAttachVolume() invoked (id=i-3B530725 vol=vol-333204B7 remote=/dev/etherd/e1.0 local=/dev/sda) [Tue Feb 23 15:18:14 2010][001762][EUCAERROR ] libvirt: server closed connection (code=38) [Tue Feb 23 15:18:14 2010][001762][EUCAERROR ] virDomainAttachDevice() failed (err=-1) XML=disk type='block'driver name='phy'/source dev='/dev/etherd/e1.0'/target dev='sda'//disk [Tue Feb 23 15:18:14 2010][001762][EUCAERROR ] ERROR: doAttachVolume() failed error=1 [Tue Feb 23 15:18:16 2010][001762][EUCAERROR ] libvirt: cannot send data: Broken pipe (code=38) [Tue Feb 23 15:18:16 2010][001762][EUCAWARN ] warning: hypervisor failed to find domain i-3B530725, will retry 4 more times [Tue Feb 23 15:18:21 2010][001762][EUCAERROR ] libvirt: cannot send data: Broken pipe (code=38) [Tue Feb 23 15:18:21 2010][001762][EUCAWARN ] warning: hypervisor failed to find domain i-3B530725, will retry 3 more times [Tue Feb 23 15:18:26 2010][001762][EUCAERROR ] libvirt: cannot send data: Broken pipe (code=38) [Tue Feb 23 15:18:26 2010][001762][EUCAWARN ] warning: hypervisor failed to find domain i-3B530725, will retry 2 more times ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- [karmic]: attaching volume to /dev/sda results in non operational node https://bugs.launchpad.net/bugs/526506 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 526506] Re: [karmic]: attaching volume to /dev/sda results in non operational node
Restarting libvirtd seemed to resolve the issue, albeit state is inconsistent thereafter. -- [karmic]: attaching volume to /dev/sda results in non operational node https://bugs.launchpad.net/bugs/526506 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 503180] Re: eucalyptus-cloud doesn't reply to requests (eucalyptus doesn't work after reboot or services restart issues due to upstart networking behavior)
I first reproduced the problem on the training cloud, then installed the PPA packages. The problem went away, the cloud is responsive within the first two minutes of restarting the frontend. -- eucalyptus-cloud doesn't reply to requests (eucalyptus doesn't work after reboot or services restart issues due to upstart networking behavior) https://bugs.launchpad.net/bugs/503180 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
Re: [Bug 519513] [NEW] UEC upgrade from 9.10 karmic to Lucid fails
On Tue, 2010-02-09 at 21:39 +, Boris Devouge wrote: - ran on 3 nodes: 'sudo apt-get clean all sudo apt-get update sudo apt-get upgrade' Any reason for using this method rather than the recommended do-release-upgrade -d procedure? -- UEC upgrade from 9.10 karmic to Lucid fails https://bugs.launchpad.net/bugs/519513 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
Re: [Bug 514198] Re: SSH key stopped working
Quite possible, the students are instructed to create a key called 'mykey' in the exercise. With this the problem can be reproduced: $ euca-add-keypair mykey2 mykey2.priv $ euca-add-keypair mykey2 mykey2.priv $ euca-run-instances -t c1.medium -k mykey2 emi-DF481077 $ ssh -i mykey2.priv 172.24.129.128 Permission denied (publickey). -- SSH key stopped working https://bugs.launchpad.net/bugs/514198 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 517086] [NEW] euca-create-volume fails at times with Error communicating with Storage Controller
Public bug reported: Happened on the Ubuntu training cloud with Ubuntu 9.10. For testing purposes for training I create 32 volumes with the following script: for i in $( seq 1 32); do sleep 5; euca-create-volume -s 1 -z classcloud; done After creating these I remove them with: for vol in $(euca-describe-volumes | cut -c8-20 | xargs); do euca-delete-volume $vol; done I regularly see this error Volume: Error communicating with Storage Controller: CreateStorageVolume:Internal Error. I run the two scripts four times with these results: first run: 31 volumes created second run: 29 volumes created third run: 25 volumes created fourth run: 25 volumes created I counted the volumes with euca-describe-volumes | grep avail | wc -l As the last run was completely without the error 'Volume: Error communicating ...' something else is hindering the volumes from being created as well. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- euca-create-volume fails at times with Error communicating with Storage Controller https://bugs.launchpad.net/bugs/517086 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 491437] Re: Wrong URL port suggested for Landscape registration
From the extra tab select 'Register this cloud with Landscape' ** Attachment added: UEC-landscape-start.png http://launchpadlibrarian.net/38613962/UEC-landscape-start.png -- Wrong URL port suggested for Landscape registration https://bugs.launchpad.net/bugs/491437 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 491437] Re: Wrong URL port suggested for Landscape registration
From there the Landscape registration form is filled in incorrectly with the port 8443. ** Attachment added: UEC-landscape-wrongURL.png http://launchpadlibrarian.net/38613978/UEC-landscape-wrongURL.png -- Wrong URL port suggested for Landscape registration https://bugs.launchpad.net/bugs/491437 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
Re: [Bug 514198] Re: SSH key stopped working
The sshd is started, the last few lines from euca-get-console-output: ec2: ec2: # ec2: -BEGIN SSH HOST KEY FINGERPRINTS- ec2: 2048 c5:e6:f6:21:16:bf:b4:d8:00:fa:1b:ad:29:12:86:de /etc/ssh/ssh_host_rsa_key.pub (RSA) ec2: 1024 b9:c0:86:af:2f:70:8b:58:0e:65:90:c8:96:1e:53:9d /etc/ssh/ssh_host_dsa_key.pub (DSA) ec2: -END SSH HOST KEY FINGERPRINTS- ec2: # * Starting OpenBSD Secure Shell server sshd * Running EC2 user data -- SSH key stopped working https://bugs.launchpad.net/bugs/514198 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 514198] [NEW] SSH key stopped working
Public bug reported: On UEC on Ubuntu 9.10 the following problem occured during last week's training session: A student created a key and it worked fine. After some time it stopped working, e.g. the key can no longer be used to log into an instance. The key is named mykey and specific for a certain user - note that multiple users have all a key called 'mykey', maybe this is where Eucalyptus gets confused? $ ssh -vi ./mykey.priv ubu...@172.24.129.139 OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 172.24.129.139 [172.24.129.139] port 22. debug1: Connection established. debug1: identity file ./mykey.priv type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-6ubuntu2 debug1: match: OpenSSH_5.1p1 Debian-6ubuntu2 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-8ubuntu1.2 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host '172.24.129.139' is known and matches the RSA host key. debug1: Found key in /home/student/.ssh/known_hosts:2 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: ./mykey.priv debug1: read PEM private key done: type RSA debug1: Authentications that can continue: publickey debug1: No more authentication methods to try. Permission denied (publickey). ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- SSH key stopped working https://bugs.launchpad.net/bugs/514198 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 514203] [NEW] Changing networking mode left cloud non working
Public bug reported: During the UEC class this week using Ubuntu 9.10 the following problem surfaced: The cloud was fully operational. The networking mode was changed from MANAGED_NOVLAN to SYSTEM. After rebooting the front-end and node no instance could be started anymore. The instance was left pending and then terminated after a few minutes. Next the networking mode was changed back to MANAGED_NOVLAN. Neither a reboot nor a restart of eucalyptus on front end and node changed the behaviour, e.g. no more instances can be started. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- Changing networking mode left cloud non working https://bugs.launchpad.net/bugs/514203 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 514203] Re: Changing networking mode left cloud non working
*** This bug is a duplicate of bug 464384 *** https://bugs.launchpad.net/bugs/464384 The complete cloud (frontend and node) was rebooted. -- Changing networking mode left cloud non working https://bugs.launchpad.net/bugs/514203 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
Re: [Bug 514198] Re: SSH key stopped working
On Fri, 2010-01-29 at 19:26 +, Dustin Kirkland wrote: ... Or, rather, did they create and use instances with that key, and then later, create instances but not be able to use that key? This I meant with stopped working. -- SSH key stopped working https://bugs.launchpad.net/bugs/514198 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 514203] Re: Changing networking mode left cloud non working
*** This bug is a duplicate of bug 464384 *** https://bugs.launchpad.net/bugs/464384 You are right, it is a duplicate, the following worked: $ sudo restart eucalyptus CLEAN=1 -- Changing networking mode left cloud non working https://bugs.launchpad.net/bugs/514203 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 464418] Re: Official UEC image fails to boot
I cannot reproduce the problem anymore with the cloud I've got currently running. I suggest to invalidate the bug. -- Official UEC image fails to boot https://bugs.launchpad.net/bugs/464418 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
Re: [Bug 503180] Re: eucalyptus-cloud doesn't reply to requests
I've seen similar problems in the past, but waiting for some extended time (15 minutes) solved it. In that time the Web UI was also not working, the admin user was reported to not exist. -- eucalyptus-cloud doesn't reply to requests https://bugs.launchpad.net/bugs/503180 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 498174] [NEW] Maximum number of 8 loopback devices low for SC
Public bug reported: The default Ubuntu kernel provides only 8 loopback devices. Setting more is possible with the max_loop=number on the kernel boot parameters line in /boot/grub/grub.cfg. It would be great if this can be done automagically for a host configured as Storage Controller. Background is that we had a training class this week where with 6 students creating volumes we were running out of volumes quickly. I realise that this might happen in larger clouds with many instances much faster. ** Affects: eucalyptus (Ubuntu) Importance: Wishlist Status: New ** Changed in: eucalyptus (Ubuntu) Importance: Undecided = Wishlist -- Maximum number of 8 loopback devices low for SC https://bugs.launchpad.net/bugs/498174 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 498174] Re: Maximum number of 8 loopback devices low for SC
I just learned that the number of loop back devices is managed dynamically by the kernel. However, the number of actual loop back devices in /dev/ is set to 8 by default. Creating new ones can be done with $ sudo mknod b 7 number /dev/loopnumber -- Maximum number of 8 loopback devices low for SC https://bugs.launchpad.net/bugs/498174 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
Re: [Bug 497716] Re: Lucid: walrus not automatically discovered
I cannot repeat the problem today. After specifying the hostname to 'node01' the next screeen says 'Select cloud installation mode' and informs that no eucalyptus cloud controller was found on your network. Albeit the cloud controller is up and running on another machine. I then specify the cloud controller's IP address. Today I get the suggestion 'Node controller', which is correct. -- Lucid: walrus not automatically discovered https://bugs.launchpad.net/bugs/497716 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 497716] [NEW] Lucid: walrus not automatically discovered
Public bug reported: I just installed UEC with the Lucid installer. First I installed the front end with clc, walrus, cc and sc. Then the node. The node told me that it cannot find walrus and the installer suggested to me to install it first. I checked ps aux | grep avahi on the frontend and the avahi line for walrus looks different from the others. It says avahi-publish -s 192.168.1.120 instead of avahi-publish -s TestCloud. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- Lucid: walrus not automatically discovered https://bugs.launchpad.net/bugs/497716 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 497087] [NEW] Redundancy for cloud and cluster controller
Public bug reported: A question that came up in every UEC class I've run so far was how to make the cloud and cluster controller redundant, so the cloud is more resilient to failures of those components. Are there any suggestions out there how to achieve this? ** Affects: eucalyptus (Ubuntu) Importance: Wishlist Status: New ** Changed in: eucalyptus (Ubuntu) Importance: Undecided = Wishlist -- Redundancy for cloud and cluster controller https://bugs.launchpad.net/bugs/497087 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 491437] [NEW] Wrong URL port suggested for Landscape registration
Public bug reported: When using the services tab in the UEC webUI and registering with Landscape, the 8443 port is suggested instead of the correct 8773. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- Wrong URL port suggested for Landscape registration https://bugs.launchpad.net/bugs/491437 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 482716] Re: eucalyptus-cloud not starting when separating cloud and cc
At the moment not, as I do not have access to that cloud environment any longer. From UDS I take that we do not fully support the separation of cloud and cluster controller in UEC. This needs to be done by changing the eucalyptus.conf files. -- eucalyptus-cloud not starting when separating cloud and cc https://bugs.launchpad.net/bugs/482716 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 464418] Re: Official UEC image fails to boot
This seems to be cloud specific to the one at my home. I have the image running on a different cloud and it works fine there. -- Official UEC image fails to boot https://bugs.launchpad.net/bugs/464418 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 480048] Re: euca-register fails with syntax error
grep -i deadlock /var/log/eucalyptus/* /tmp/deadlock ** Attachment added: deadlock http://launchpadlibrarian.net/35653868/deadlock -- euca-register fails with syntax error https://bugs.launchpad.net/bugs/480048 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
Re: [Bug 470355] Re: ec2-bundle-vol and ec2-upload-bundle result in non accepted manifest
On Tue, 2009-11-10 at 08:51 +, Eric Hammond wrote: Torsten: What AMI id are you starting with? This one was a Jaunty image created with vmbuilder. part file looks like: root 2000 swap 1 and first boot looks like: while (! ping -c 1 archive.ubuntu.com); do sleep 1; done apt-get -y install openssh-server ifconfig -a -- ec2-bundle-vol and ec2-upload-bundle result in non accepted manifest https://bugs.launchpad.net/bugs/470355 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 480048] [NEW] euca-register fails with syntax error
Public bug reported:
After creating a homemade Karmic image with vmbuilder, it fails to
register with:
euca-register karmic-homemade/root.img.manifest.xml
Warning: failed to parse error message from AWS: unknown:1:49: syntax error
Traceback (most recent call last):
File /usr/bin/euca-register, line 95, in module
main()
File /usr/bin/euca-register, line 87, in main
euca.display_error_and_exit('%s' % ex)
File /usr/lib/python2.6/dist-packages/euca2ools/__init__.py, line 996, in
display_error_and_exit
dom = minidom.parseString(msg)
File /usr/lib/python2.6/xml/dom/minidom.py, line 1928, in parseString
return expatbuilder.parseString(string)
File /usr/lib/python2.6/xml/dom/expatbuilder.py, line 940, in parseString
return builder.parseString(string)
File /usr/lib/python2.6/xml/dom/expatbuilder.py, line 223, in parseString
parser.Parse(string, True)
xml.parsers.expat.ExpatError: syntax error: line 1, column 49
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
euca-register fails with syntax error
https://bugs.launchpad.net/bugs/480048
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 480048] Re: euca-register fails with syntax error
Here the relevant parts from history: 64 export http_proxy=http://10.153.104.60:3128 65 sudo vmbuilder xen ubuntu 66 sudo vmbuilder xen ubuntu --part ./part --firstboot ./firstboot 67 ls 68 euca-bundle-image -i ubuntu-xen/root.img 69 euca-upload-bundle -m /tmp/root.img.manifest.xml -n karmic-homemade 70 euca-upload-bundle -m /tmp/root.img.manifest.xml -b karmic-homemade 71 euca-register karmic-homemade/root.img.manifest.xml 72 euca-upload-bundle -m /tmp/root.img.manifest.xml -b karmic-homemade 73 euca-register karmic-homemade/root.img.manifest.xml 74 history -- euca-register fails with syntax error https://bugs.launchpad.net/bugs/480048 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 480048] Re: euca-register fails with syntax error
Here the image manifest. ** Attachment added: root.img.manifest.xml http://launchpadlibrarian.net/35480755/root.img.manifest.xml -- euca-register fails with syntax error https://bugs.launchpad.net/bugs/480048 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 480048] Re: euca-register fails with syntax error
This might be unrelated to euca-register, I get the same error with
euca-describe-availability-zones:
$ euca-describe-availability-zones
Warning: failed to parse error message from AWS: unknown:1:49: syntax error
Traceback (most recent call last):
File /usr/bin/euca-describe-availability-zones, line 106, in module
main()
File /usr/bin/euca-describe-availability-zones, line 102, in main
euca.display_error_and_exit('%s' % ex)
File /usr/lib/python2.6/dist-packages/euca2ools/__init__.py, line 996, in
display_error_and_exit
dom = minidom.parseString(msg)
File /usr/lib/python2.6/xml/dom/minidom.py, line 1928, in parseString
return expatbuilder.parseString(string)
File /usr/lib/python2.6/xml/dom/expatbuilder.py, line 940, in parseString
return builder.parseString(string)
File /usr/lib/python2.6/xml/dom/expatbuilder.py, line 223, in parseString
parser.Parse(string, True)
xml.parsers.expat.ExpatError: syntax error: line 1, column 49
--
euca-register fails with syntax error
https://bugs.launchpad.net/bugs/480048
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 480048] Re: euca-register fails with syntax error
After a reboot, 'euca-describe-availability-zones verbose' worked fine. 'euca-register' still fails, with a different error: $ euca-register karmic-homemade/root.img.manifest.xmlWarning: failed to parse error message from AWS: unknown:1:0: syntax error EC2ResponseError: 403 Forbidden Failure: 403 Forbidden -- euca-register fails with syntax error https://bugs.launchpad.net/bugs/480048 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 480048] Re: euca-register fails with syntax error
After a wait the last error went away and euca-register worked. -- euca-register fails with syntax error https://bugs.launchpad.net/bugs/480048 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
