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

Fixed datastore name mapping issue #5920

Merged
merged 1 commit into from
May 29, 2019
Merged

Fixed datastore name mapping issue #5920

merged 1 commit into from
May 29, 2019

Conversation

prydin
Copy link
Contributor

@prydin prydin commented May 28, 2019

Required for all PRs:

  • Signed CLA.
  • Associated README.md updated.
  • Has appropriate unit tests.

LUN IDs were not correctly mapped to datastore names. The mapping code was using an obsolete mapping table that is no longer populated. Removed the obsolete table and changed to code to using the new version of the mapping table instead.

This fixes issue #5881

@danielnelson danielnelson added this to the 1.11.0 milestone May 29, 2019
@danielnelson danielnelson added area/vsphere fix pr to fix corresponding bug labels May 29, 2019
@danielnelson danielnelson merged commit fa492e0 into influxdata:master May 29, 2019
hwaastad pushed a commit to hwaastad/telegraf that referenced this pull request Jun 13, 2019
bitcharmer pushed a commit to bitcharmer/telegraf that referenced this pull request Oct 18, 2019
athoune pushed a commit to bearstech/telegraf that referenced this pull request Apr 17, 2020
@playground-io
Copy link

is this issue, back again in version 1.15.1-1?
I'm having it, LUN and DSNAME have the same content.

idohalevi pushed a commit to idohalevi/telegraf that referenced this pull request Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vsphere fix pr to fix corresponding bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants