Bug 1610908 - Unable to create compute in RHV 4.2
Summary: Unable to create compute in RHV 4.2
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - RHEV
Version: 6.3.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-01 15:23 UTC by Gianfranco Sigrisi
Modified: 2019-09-26 14:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-02 04:49:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gianfranco Sigrisi 2018-08-01 15:23:56 UTC
Description of problem:

Hi,
I'm unable to create a new vm from Satellite 6.3.2 to RHV 4.2. 

From the production.log:

 | OVIRT::OvirtException: 404 Resource Not Found

From engine.log:

Client from address .. is using version 3 of the API, which has been deprecated since version 4.0 of the engine, and will no longer be supported starting with version 4.3. Make sure to update that client to use a supported versions of the API and the SDKs, before upgrading to version 4.3 of the engine.

Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:
1. Add a Compute Resource type RHV
2. Engine endpoint with api/v3 (as described in the DOC)
3. Try to create a new vm from Satellite - Create Host - Deploy ON RHV

Actual results:

Failed to create compute: 404 Resource not Found

Expected results:

VM is created

Additional info:

Comment 1 orabin 2018-08-02 04:49:05 UTC
In 6.3 there is no support for RHV API v4.
To use api v3 with a RHV 4.x change the url to: https://rhv-example/api/v3

Support for v4 will be available in Satellite 6.4.

Comment 2 Ivan Necas 2018-10-18 14:10:23 UTC
I don't think the request of this BZ was to use API v4, but I believe we are tracking the fix for this issue in https://bugzilla.redhat.com/show_bug.cgi?id=1637955


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