Skip to content
This repository

nimbus-admin -l and current-reservations.txt synchronization problem #113

Closed
buzztroll opened this Issue August 16, 2012 · 1 comment

2 participants

John Bresnahan Pierre Riteau
John Bresnahan
Collaborator

This tends to happen when a VMM node fails and then comes back up. The VMs Nimbus started are gone, but Nimbus doesn't seem to realize that.

Specifically on Alamo right now (Nimbus 2.9), VM instance 959 is shown in current-reservations.txt, there are repeating entries like below in services.log:

2012-08-16 08:42:08,898 INFO impls.InstanceResourceImpl [pool-3-thread-2,remove:767] [NIMBUS-EVENT][id-959]: destroy begins
2012-08-16 08:42:14,902 INFO impls.InstanceResourceImpl [pool-3-thread-2,remove:767] [NIMBUS-EVENT][id-959]: destroy begins

But that instance doesn't appear in "nimbus-admin -l".

Pierre Riteau
Owner

This problem is not related to current-reservations.txt. The instance information is in the Derby database.

What happens is that the method called by nimbus-admin to list all instances ends up calling impls.WorkspaceHomeImpl:find. This method tries to destroy expired instances and throws an exception for those.
Because this exception is thrown, instances are not included in the result of nimbus-admin.

Should we show expired instances that couldn't be destroyed in the nimbus-admin output?

Pierre Riteau priteau closed this issue from a commit August 17, 2012
Pierre Riteau Include expired but non-destroyed VMs in nimbus-admin output
VMs which expired but failed to be destroyed (for example when the VMM
is offline) were not included in the nimbus-admin output because the
destroy tentative threw an exception which removed them from the list.

With this commit the exception is thrown only when the destroy action
has succeeded.

Closes #113.
b926c28
Pierre Riteau priteau closed this in b926c28 August 17, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.