-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some agents aren't deallocated #74
Comments
@tom-dudley, I see that you are using the ARM plugin to start these machines, but in the agent log from vm Could you please verify that you're using latest version of ARM plugin and check that you don't have installed Azure Classic plugin? You could do that on the Administration -> Plugins List page. |
We have the following relevant plugins on our server:
I assume the first plugin is the Classic plugin and we're fine to remove it since we only use ARM (I guess they're in conflict with one another) |
@tom-dudley, yes, |
Thanks @dtretyakov , feel free to close this issue. |
I have some agents which are shutting down, but not being deallocated.
This is a similar, if not the same, issue as #64 however the fix given there doesn't work in my case. We did originally have a different idle timeout to our current one, but the agents which are failing to deallocate where created after the timeout was last changed.
Here is the relevant server log, where you can see that
tcagent3
has been found to be stopped. You can also see an agent which was successfully deallocated (tcagent2
) gets theStopping virtual machine tcagent2
message. There is not aStopping virtual machine tcagent3
message.Here is the agent log from
tcagent3
where we can see it has decided to shutdown. This log is a bit odd since our timeout is currently 15 minutes.Since the
Stopping virtual machine tcagent3
message never appears in the server log, theterminateInstance
method doesn't seem to be getting called for it, despite the agent deciding to shutdown. The shutdown of the agent VM causes it to be in the 'Stopped (incurring charges)' state but since the server-side plugin didn't enterterminateInstance
(and thenstopVmAsync
), the deallocation never happens.So the bug here seems to be that the agent is shutting down when the server-side plugin isn't in
terminateInstance
. I don't know why this is the case. Let me know if I can provide further logs which might be of use.The text was updated successfully, but these errors were encountered: