[Bug 728018] Re: 10.04 LTS: Failure to start instance due to network address failure

2015-02-13 Thread M.Morana
** Changed in: eucalyptus (Ubuntu) Status: Triaged = Invalid -- 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

[Bug 728018] Re: 10.04 LTS: Failure to start instance due to network address failure

2011-03-10 Thread Scott Moser
** Changed in: eucalyptus (Ubuntu) Importance: Undecided = Medium ** Changed in: eucalyptus (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu.

[Bug 728018] Re: 10.04 LTS: Failure to start instance due to network address failure

2011-03-08 Thread Torsten Spindler
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

[Bug 728018] Re: 10.04 LTS: Failure to start instance due to network address failure

2011-03-07 Thread Torsten Spindler
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

[Bug 728018] Re: 10.04 LTS: Failure to start instance due to network address failure

2011-03-04 Thread Torsten Spindler
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

[Bug 728018] Re: 10.04 LTS: Failure to start instance due to network address failure

2011-03-04 Thread Torsten Spindler
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

[Bug 728018] Re: 10.04 LTS: Failure to start instance due to network address failure

2011-03-03 Thread Torsten Spindler
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 ]

[Bug 728018] Re: 10.04 LTS: Failure to start instance due to network address failure

2011-03-02 Thread Torsten Spindler
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

[Bug 728018] Re: 10.04 LTS: Failure to start instance due to network address failure

2011-03-02 Thread Torsten Spindler
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