Bug 1587905

Summary: RHEV API v4 VM Import: undefined method `update_vm'
Product: Red Hat Satellite Reporter: Lukáš Hellebrandt <lhellebr>
Component: Compute Resources - RHEVAssignee: orabin
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: inecas, orabin, pcreech
Target Milestone: 6.4.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-fog-ovirt-1.1.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:01:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
foreman-tail.log none

Description Lukáš Hellebrandt 2018-06-06 09:48:35 UTC
Created attachment 1448237 [details]
foreman-tail.log

Description of problem:
When importing a VM from RHEV using APIv4, a NoMethodError appears in log and in WebUI and the action fails.

Version-Release number of selected component (if applicable):
Sat 6.4 snap 6

How reproducible:
Deterministic

Steps to Reproduce:
1. Have a Sat with RHEV CR with 'Use APIv4' checked and some VM in that RHEV
2. Go to CR -> <cr> -> VM tab, in the dropdown menu of some VM, click Import
3. Fill in the rest of the form, click Submit while tailing logs

Actual results:
Traceback, error, fail

Expected results:
VM added successfully

Additional info:
Tested also with APIv3, it does NOT happen with it

Comment 1 orabin 2018-06-06 12:30:49 UTC
Created redmine issue http://projects.theforeman.org/issues/23836 from this bug

Comment 3 Satellite Program 2018-06-06 14:07:42 UTC
Upstream bug assigned to orabin

Comment 4 Satellite Program 2018-06-06 14:07:45 UTC
Upstream bug assigned to orabin

Comment 6 Lukáš Hellebrandt 2018-07-16 14:23:31 UTC
Verified with Sat 6.4 snap 12.

Used reproducer from OP, there was no error, no traceback and the host has been added correctly.

Comment 7 Bryan Kearney 2018-10-16 19:01:51 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927