Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

uneeded 'VM has already been deleted or has not been completely ' traceback in the log #1457

Closed
msterin opened this issue Jun 21, 2017 · 3 comments
Assignees
Labels
Milestone

Comments

@msterin
Copy link
Contributor

msterin commented Jun 21, 2017

Each test run generates an error below in the log. This is totally normal situation (VM was powered down and then deleted right away) and we should not log it as an error.
In fact, it feel like a debug message, or at worst Info with explanation ("Most likely a VM was powered down and then deleted right away"

//CC @pshahzeb

06/21/17 22:10:54 216439 [VMChangeListener] [ERROR  ] VMChangeListener: error (vmodl.fault.ManagedObjectNotFound) {
   dynamicType = <unset>,
   dynamicProperty = (vmodl.DynamicProperty) [],
   msg = "The object 'vim.VirtualMachine:118' has already been deleted or has not been completely created",
   faultCause = <unset>,
   faultMessage = (vmodl.LocalizableMessage) [],
   obj = 'vim.VirtualMachine:118'
}
06/21/17 2
@msterin msterin added this to the 0.16 milestone Jun 27, 2017
@msterin msterin added the P1 label Jun 27, 2017
@msterin
Copy link
Contributor Author

msterin commented Jun 27, 2017

Can you please get it fixed ? It block any reasonable analysis of error logs for test-esx makefile target, as the whole log is polluted with these meaningless messages.

@pshahzeb
Copy link
Contributor

Sure. Sending out a PR.

@msterin
Copy link
Contributor Author

msterin commented Jun 27, 2017

Thanks !

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants