Bug 1713394 - Retry to add conversion host via UI shows API error
Summary: Retry to add conversion host via UI shows API error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: V2V
Version: 5.10.5
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.11.0
Assignee: Daniel Berger
QA Contact: Shveta
Red Hat CloudForms Documentation
URL:
Whiteboard: v2v
Depends On:
Blocks: 1717023
TreeView+ depends on / blocked
 
Reported: 2019-05-23 14:36 UTC by Shveta
Modified: 2019-12-13 15:08 UTC (History)
4 users (show)

Fixed In Version: 5.11.0.7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1717023 (view as bug list)
Environment:
Last Closed: 2019-12-13 15:08:58 UTC
Category: Bug
Cloudforms Team: V2V
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Console output (309.79 KB, image/png)
2019-05-23 14:36 UTC, Shveta 		no flags Details
View All

Description Shveta 2019-05-23 14:36:21 UTC 
Created attachment 1572555 [details]
Console output

Description of problem:


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

How reproducible:


Steps to Reproduce:
1. Add conversion host via UI , SO that it fails .
2. Retry button shows up . Click on retry and provide key .
3. API error shows up. "Data {"error":{"kind":"bad_request","message":"unsupported resource_type Host","klass":"Api::BadRequestError"}}"

Actual results:


Expected results:


Additional info:
Comment 2 Shveta 2019-05-24 18:30:42 UTC 
PR with the fix ManageIQ/manageiq#18799
Comment 3 Brett Thurber 2019-05-29 14:45:53 UTC 
Link to new PR that resolves the API side:  https://github.com/ManageIQ/manageiq-api/pull/600

Waiting to be merged and include into build.
Comment 4 Daniel Berger 2019-05-29 14:56:37 UTC 
Also https://github.com/ManageIQ/manageiq/pull/18819 to deal with the auth_user param.
Comment 6 Yadnyawalk Tale 2019-06-14 13:22:59 UTC 
Verified on: 5.11.0.8.20190611155126_01e077e
Note You need to log in before you can comment on or make changes to this bug.