Bug 1752732 - RHV Provider fails to collect data from RHV 4.3 if a snapshot of 4.0 version exists for any VM
Summary: RHV Provider fails to collect data from RHV 4.3 if a snapshot of 4.0 version ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.10.9
Hardware: All
OS: Linux
medium
high
Target Milestone: GA
: 5.10.14
Assignee: Roberto Ciatti
QA Contact: Angelina Vasileva
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On: 1755869
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-17 06:15 UTC by Tomas Dosek
Modified: 2020-01-21 19:54 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-21 19:54:59 UTC
Category: Bug
Cloudforms Team: RHEVM
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tomas Dosek 2019-09-17 06:15:47 UTC
Description of problem:

[Customer scenario]
CFME EVM log points to Failure to load VM data due to VM64BitMaxMemorySizeInMB value being invalid (4.0). Same happens for the ResumeBehaviorSupported value as well


Version-Release number of selected component (if applicable):
RHV 4.3.5, CFME 5.10.9 Virtual appliance for RHV (unmodified content)


How reproducible:
Specific setup is require

Steps to Reproduce:
1. Have a RHV VM with snapshot that has version 4.0
2. Add new provider


Actual results:
See no data for the provider (no VMs, no Hosts, nothing...)

Expected results:
Provider is imported correctly.

Additional info:

To workaround the issue following options were injected on RHV Maneger side
(but note these values are not supposed to be in the DB anymore by current RHV standard).

insert into vdc_options (option_name,option_value,version) values('ResumeBehaviorSupported',false,'4.0');
insert into vdc_options (option_name,option_value,version) values('VM64BitMaxMemorySizeInMB',4194304,'4.0');

Comment 12 Martin Perina 2019-10-30 13:44:06 UTC
Moving to POST as there is no fix on CFME side, we just need to verify that the issue is fixed in RHV 4.3.7 as tracked in BZ1755869 and no additional errors appears on CFME side


Note You need to log in before you can comment on or make changes to this bug.