Bug 1842806

Summary: [v2v] conversion host detail is not visible on conversion host page after configuration widget gets closed.
Product: Red Hat CloudForms Management Engine Reporter: Md Nadeem <mnadeem>
Component: V2VAssignee: Fabien Dupont <fdupont>
Status: CLOSED WONTFIX QA Contact: Md Nadeem <mnadeem>
Severity: high Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: unspecified    
Version: 5.11.6CC: bthurber, dmetzger, fdupont, mturley
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-04 07:03:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: V2V Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1827127    

Description Md Nadeem 2020-06-02 07:19:41 UTC 
Description of problem:

While configuring a conversion host(having no ip associated), the detail not appeared on conversion host page once the configuration widget gets closed. 

Note: We required this kind of setup to verify the BZ#1827127

I expected the failed details should be visible as row in conversion host page.

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

cfme version: 5.11.6.0

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Mike Turley 2020-06-02 16:36:03 UTC 
@Md Nadeem,

When you submitted the configuration wizard, did you get any kind of feedback at all, like an error message? Can you provide details on how I can reproduce this (what inputs I need to put into the wizard)?
Comment 3 Mike Turley 2020-06-02 16:41:29 UTC 
Ah okay, I tried it with fake authentication data (since we expect it to fail anyway) and I see the HTTP response is this:

```
200 OK
{"results":[{"success":false,"message":"Vm 'auto-conv-osp-instance3' doesn't have a hostname or IP address in inventory","href":"https://10.8.198.27/api/conversion_hosts/"}]}
```

I don't think we wrote code in the UI to handle a `"success": false` response to even starting the conversion host task, but I'm surprised this response has the "200 OK" status. If the response had an HTTP error status, CloudForms would have opened an error modal by default with the response body.

Fabien, do you think we should add logic to the UI to handle responses of this form (200 OK, success: false), or should this be considered a backend bug or wontfix?
Comment 4 Fabien Dupont 2020-06-04 07:03:06 UTC 
It's a normal behavior of CloudForms. What HTTP 200 with "success: false" means is that the error is normal and handled by the backend, hence the HTTP 200, but it still says the request failed with a reason. We won't spend time to change that. Closing as WONTFIX.