Bug 1593228 - [v2v] 400 Bad Request after first enablement of v2v migration UI
Summary: [v2v] 400 Bad Request after first enablement of v2v migration UI
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.9.4
Assignee: Brett Thurber
QA Contact: Yadnyawalk Tale
URL:
Whiteboard: v2v
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-20 10:19 UTC by Yadnyawalk Tale
Modified: 2018-06-29 11:09 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-29 11:09:11 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
400_error.png (79.87 KB, image/png)
2018-06-20 10:19 UTC, Yadnyawalk Tale
no flags Details

Description Yadnyawalk Tale 2018-06-20 10:19:00 UTC
Created attachment 1453174 [details]
400_error.png

Description of problem:
I got this issue while verifying BZ1583819. 400 bad request error's modal appearing when you set transformation value to true from advanced settings.

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

How reproducible:
100%

Steps to Reproduce:
(Use fresh appliance) 
1. Administrator (top right) -> Configuration - > Advanced tab
2. Search `:transformation`, set its value true
3. restart appliance
(You should get `migration` in main navigation now)
4. Navigate to Compute > Migration 
You will get that error. 

Actual results:
Error is appearing

Expected results:
Should not appear that error

Additional info:
Its impact is kinda none, I can do all the normal operations by closing modal but just this error pop-up looks bad. Let me in case any logs requires.

Comment 4 Yadnyawalk Tale 2018-06-29 11:09:11 UTC
@Brett, I checked on latest downstream/5.9.3.3.20180627151410_682cecf and issue is no more reproducible. Closing this issue since it WORKSFORME!

Thanks a lot guys!


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