VMWare provider does not work in Kasparov 2 #747
Comments
|
@andersulrich what version of vSphere are you using? |
|
@andersulrich this is due to vmware-archive/rbvmomi#208 which I proposed vmware-archive/rbvmomi#209 as a fix but VMware has since archived the gem. We've forked it https://github.com/ManageIQ/rbvmomi2 and have fixed this in ManageIQ/rbvmomi2#4 |
|
@agrare Thank you for the response. As we are upgrading from Ivanchuk to Kasparov, would it be possible to upgrade to Jansta instead? Maybe the VMware provider works the old way in Jansta? Would it help us to get it working at this moment? |
|
Hey @andersulrich the issue isn't with any change in ManageIQ but rather using a vSphere version that isn't supported by the VMware SDK so changing the ManageIQ version won't help |
|
This issue has been mentioned on ManageIQ Forum. There might be relevant details there: https://talk.manageiq.org/t/vmware-provider-does-not-work-in-kasparov-2/5514/2 |
Hi, I am looking for an advice regarding our problem.
We recently tried to upgrade from Ivanchuk (ivanchuk-3.20200226215823_dbb486d) to Kasparov 2 (kasparov-2.20210716154634_ddad0d6)
Everything seems to be working fine but our VMWare providers cannor refresh any data from VMWare with the following error:
[----] E, [2021-09-17T17:20:40.511472 #185236:2aac4e64290c] ERROR – : MIQ(ManageIQ::Providers::Vmware::InfraManager::Inventory::Collector#vim_collector) EMS: [VMware HCI vamgkb200], id: [1] Refresh failed [----] E, [2021-09-17T17:20:40.511752 #185236:2aac4e64290c] ERROR – : [RuntimeError]: unknown VMODL type VsanDatastoreInfo Method:[block (2 levels) in class:LogProxy] [----] E, [2021-09-17T17:20:40.512750 #185236:2aac4e64290c] ERROR – : /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/type_loader.rb:105:in make_type' /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/type_loader.rb:67:in block in get’ /usr/share/ruby/monitor.rb:235:in mon_synchronize' /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/type_loader.rb:65:in get’ /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:87:in deserialize' /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:124:in block in traverse_data’ /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:106:in each' /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:106:in traverse_data’ /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:90:in deserialize' /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:119:in block in traverse_data’ /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:106:in each' /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:106:in traverse_data’ /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:90:in deserialize' /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:119:in block in traverse_data’ /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:106:in each' /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:106:in traverse_data’ /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:90:in deserialize' /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:119:in block in traverse_data’ /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:106:in each' /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:106:in traverse_data’ /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/deserialization.rb:90:in deserialize' /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/connection.rb:70:in block in parse_response’ /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/connection.rb:70:in map' /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/connection.rb:70:in parse_response’ /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/connection.rb:92:in call' /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/basic_types.rb:213:in _call’ /opt/manageiq/manageiq-gemset/gems/rbvmomi-3.0.0/lib/rbvmomi/basic_types.rb:76:in block (2 levels) in init' /opt/manageiq/manageiq-gemset/bundler/gems/manageiq-providers-vmware-42e38d3d8685/app/models/manageiq/providers/vmware/infra_manager/inventory/collector.rb:174:in wait_for_updates’ /opt/manageiq/manageiq-gemset/bundler/gems/manageiq-providers-vmware-42e38d3d8685/app/models/manageiq/providers/vmware/infra_manager/inventory/collector.rb:118:in monitor_updates' /opt/manageiq/manageiq-gemset/bundler/gems/manageiq-providers-vmware-42e38d3d8685/app/models/manageiq/providers/vmware/infra_manager/inventory/collector.rb:106:in targeted_refresh’ /opt/manageiq/manageiq-gemset/bundler/gems/manageiq-providers-vmware-42e38d3d8685/app/models/manageiq/providers/vmware/infra_manager/inventory/collector.rb:62:in vim_collector' /opt/manageiq/manageiq-gemset/bundler/gems/manageiq-providers-vmware-42e38d3d8685/app/models/manageiq/providers/vmware/infra_manager/inventory/collector.rb:48:in block in vim_collector_thread’We tried to investigate but so far with no luck.
Anyone experienced such problem or has an idea how to resolve it?
Thanks a lot!
The text was updated successfully, but these errors were encountered: