Bug 974051

I struggled with this issue a lot, trying to reproduce it in 3.0 and didn't always get the "model server went away" error after lots of testing with small instances (64MB mem / 1GB storage). I got it a while ago but can't get the same behaviour again.

Could you please tell me more on how could I actually reproduce this in Grizzly.
Which flavor did you use?
Whics image did you use to get this error?
Everything else would be more than welcome.


In 4.0 I never got this issue after numerous tests.

I have only worked with Havana and not grizzly... 
flavour was 1 (tiny)
these images no longer exist

not sure what else to give you... two computes -> 10 instances on each -> try to create snapshots for each instance

I'm sorry, but I cannot reproduce this on my local setup after countless times.
I had lots of issues with getting myself in a situation where I can test this, and probably require more resources than I have on my laptop, but after managing that, I couldn't get the instances to go in shutoff state.

Could you please provide me with access to the machines where I can reproduce and debug this.

After speaking to Ami today I realised that I did open this bug on Grizzly. 
I tested this with Vladan in Havana and it no longer reproduced in Havana so I think we can close this.

I agree, the described behaviour is unreachable by doing snapshots of 10 instances running on 2 hosts, so I guess we can close this bug.

However, we managed to reproduce this behaviour with Dafna in Havana by snapshoting multiple instances and then opening a VNC console for one of them. All of the instances that were on that node got into Shutoff state.

Dafna please correct me if I'm wrong.

More investigation is needed on this issue. When we manage to reproduce it in 100% of the cases I suggest opening another bug and describe the steps to reproduce in detail.

For now the traceback shows only this:


 _volume_snapshot_create /usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py:1594
     % image_id, instance=instance)
   File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 309, in decorated_function
     *args, **kwargs)
   File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 2293, in snapshot_instance
     task_states.IMAGE_SNAPSHOT)
   File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 2324, in _snapshot_instance
     update_task_state)
   File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 1374, in snapshot
     virt_dom.managedSave(0)
   File "/usr/lib/python2.6/site-packages/eventlet/tpool.py", line 187, in doit
     result = proxy_call(self._autowrap, f, *args, **kwargs)
   File "/usr/lib/python2.6/site-packages/eventlet/tpool.py", line 147, in proxy_call
     rv = execute(f,*args,**kwargs)
   File "/usr/lib/python2.6/site-packages/eventlet/tpool.py", line 76, in tworker
     rv = meth(*args,**kwargs)
   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 863, in managedSave
     if ret == -1: raise libvirtError ('virDomainManagedSave() failed', dom=self)
 libvirtError: internal error received hangup / error event on socket

I'm closing this bug now because it's not reproducible in 4.0