Skip to content
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

5-6-2-VSAN-Complex nightly fail: govc datastore.vsan.dom.ls panic: nil pointer dereference #6972

Closed
AngieCris opened this issue Dec 17, 2017 · 5 comments
Labels
component/gateway/vmomi component/test Tests not covered by a more specific component label priority/p0 source/scenario Found via a scenario failure status/needs-triage The issue needs to be evaluated and metadata updated team/foundation

Comments

@AngieCris
Copy link
Contributor

AngieCris commented Dec 17, 2017

nightly 12/16/17 test group 5-6-2-VSAN-Complex

After VCH cleanup, running govc datastore.vsan.dom.ls -ds "vsanDatastore" -l -o 2>&1 gives invalid memory address or nil pointer dereference:

image

Where the panic happens according to the stack trace:
/~https://github.com/vmware/govmomi/blob/master/object/datastore.go#L410

Log:
5-6-2-VSAN-Complex.zip

@dougm

@AngieCris AngieCris added component/test Tests not covered by a more specific component label source/scenario Found via a scenario failure status/needs-triage The issue needs to be evaluated and metadata updated team/foundation labels Dec 17, 2017
@AngieCris
Copy link
Contributor Author

PR: vmware/govmomi#969

@dougm
Copy link
Member

dougm commented Dec 17, 2017

Note that the govc change does not fix the problem here, it just changes the panic to an error, the test would have still failed. Normally the task info would never be nil (the possible panic had been there for years), so something unexpected happened with the network or hostd for example.

@anchal-agrawal
Copy link
Contributor

Needs a priority - putting in Not Ready.

@hickeng
Copy link
Member

hickeng commented Jan 4, 2018

Adding the vmomi-gateway tag to issues that can/should be caught and handled below the level of the core product code. I'm still hopefully that we actually split out that component for isolation and much more targeted testing. (yes, this was in govc but the same vSphere behaviour should be handled by the product also).

@mdubya66
Copy link
Contributor

Same build has been used in every nightly since 2/23. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/gateway/vmomi component/test Tests not covered by a more specific component label priority/p0 source/scenario Found via a scenario failure status/needs-triage The issue needs to be evaluated and metadata updated team/foundation
Projects
None yet
Development

No branches or pull requests

5 participants