Closed smoeding closed 5 years ago
I just ran into that as well. I'll have a new release with the fix as soon as possible.
@smoeding Released 0.2.1 which should fix this issue. I tested it with your sample and it's working fine. Let me know if this release fixes the issue for you. Thanks for reporting!
@jrgarcia Thanks for the quick fix. Looks good to me!
@smoeding By the way, you no longer have to jump through hoops with the authentication. Check out a sample I updated here. You no longer have to set the basic_auth yourself and if you create a session, you no longer have to store the session_id and set it in the headers.
@jrgarcia I saw the sample code when I tried to find the cause for the error. Looks definitely better than the old code. For the example I just wanted to make sure the code would run on 0.1.0.
But I did update my code for the project... 👍
Describe the bug
After the update to 0.2.0 I get internal failures from the gems. For example the ClusterApi throws the following error:
How to reproduce
Use the following code to list the clusters:
Expected behavior
With release 0.1.0 of the gems I get the following output:
Now update the gems to 0.2.0:
Run again:
Versions
Dev Environment:
Additional notes
The file where the error occurs has been changed just recently: vcenter/lib/vsphere-automation-vcenter/models/vcenter_cluster_summary.rb
For the 0.2.0 release the lines 41/42 have been changed from
to
At the same time line 163 still reads:
I guess this mismatch causes the code to fall through the WHEN condition and therefore the execution reaches lines 183ff:
This is the place where the error to terminate the program is thrown.