Bug #3931
closedcompute resource vmware generates unknown VMODL type AnyType after upgrade to 1.3.2
Description
After upgrading to foreman 1.3.2 the web ui started generating error "unknown VMODL type AnyType" with anything reladet to vmware vcenter interactions.
Some googleing brought an issue with rbvmomi at version 1.8.1 to the service which causes this. The work around found was to downgrade it to version 1.6.0.
This I can confirm fixed it without any drawbacks , so far.
on debian the file edited was /usr/share/foreman/bundler.d/vmware.rb
changed the line :
_ gem "rbvmomi"_
to
_ gem "rbvmomi", '~> 1.6.0'_
and re-ran bundle install, after that restarted foreman and nginx and all was working. This ia dependency to fog if my info is correct but sofar I only found refferences on twitter.
Mind you besides in the logs :
Rendered compute_resources_vms/_error.html.erb (0.1ms)
There are no loggedd errors so far (without debugging on !!)
Updated by Dominic Cleal almost 11 years ago
- Category set to Compute resources
- Translation missing: en.field_release set to 2
Tentatively pinning to 1.4.0.. would be interested in any more reports of this. We haven't updated RPMs yet from 1.6.0 to 1.8.1 either.
Updated by Dominic Cleal almost 11 years ago
Updated by Dominic Cleal over 10 years ago
This should be pinned to ~> 1.6.0 in the meantime.
Updated by Anonymous over 10 years ago
- Status changed from New to Ready For Testing
- Assignee set to Anonymous
Updated by Anonymous over 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset de0804f0aa6e9aa61a223fb600a0c97d595695e7.
Updated by Dominic Cleal over 10 years ago
- Related to Refactor #5018: Unpin rbvmomi 1.6.0 added