Skip to content
This repository was archived by the owner on Jul 1, 2021. It is now read-only.

Update VMODL database #160

Merged
merged 1 commit into from
Apr 26, 2019
Merged

Update VMODL database #160

merged 1 commit into from
Apr 26, 2019

Conversation

jrgarcia
Copy link
Contributor

It looks like 2.1.0 introduced a few changes to the VMODL database that
broke usage for several people. This update should fix the issue by
adding some of the things that are missing back into the VMODL database
file.

Fixes #157, #159

Signed-off-by: J.R. Garcia [email protected]

It looks like 2.1.0 introduced a few changes to the VMODL database that
broke usage for several people. This update should fix the issue by
adding some of the things that are missing back into the VMODL database
file.

Fixes #157, #159

Signed-off-by: J.R. Garcia <[email protected]>
@jrgarcia
Copy link
Contributor Author

@agrare, @srobroek, @seandilda Can you all test this PR to see if it resolves the issue you are seeing? I'd like to overhaul the process that generates this VMODL file, but I'd like to go ahead and get this resolved for you all in the meantime. Thanks!

@agrare
Copy link
Contributor

agrare commented Apr 22, 2019

@jrgarcia 👍 fixes my issue thanks!

@srobroek
Copy link

srobroek commented Apr 23, 2019 via email

@jrgarcia
Copy link
Contributor Author

@srobroek Ok. I'll probably merge this in tomorrow and push out a new release. If this ends up not fixing your issue, just reopen it and I'll take a look.

@jrgarcia jrgarcia merged commit 32cc321 into master Apr 26, 2019
@jrgarcia jrgarcia deleted the vmodl-update branch August 25, 2020 15:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

esxcli option not working
3 participants