Bug 1383171 - Improve flash message when creating cloud subnet
Summary: Improve flash message when creating cloud subnet
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Gilles Dubreuil
QA Contact: Aziza Karol
URL:
Whiteboard: ui:flash_msg:sdn
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-10 05:42 UTC by Aziza Karol
Modified: 2017-01-24 08:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-24 08:58:44 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)

Description Aziza Karol 2016-10-10 05:42:20 UTC
Created attachment 1208709 [details]
flash message

Description of problem:


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

How reproducible:
100%

Steps to Reproduce:
1.Navigate to networks->subnets->create a new subnet
2.
3.

Actual results:
Unable to create Cloud Subnet "test_subet_az": Expected([201]) <=> Actual(400 Bad Request) excon.error.response :body => "{\"NeutronError\": {\"message\": \"Invalid input for operation: Requested subnet with cidr: 10.8.58.0/23 for network: b11007bc-2fb6-4d12-a2b1-6090994c00f4 overlaps with another subnet.\", \"type\": \"InvalidInput\", \"detail\": \"\"}}" :cookies => [ ] :headers => { "Content-Length" => "220" "Content-Type" => "application/json; charset=UTF-8" "Date" => "Mon, 10 Oct 2016 05:37:01 GMT" "X-Openstack-Request-Id" => "req-0620268a-b323-4601-8cd4-4895891de4a9" } :host => "10.8.58.70" :local_address => "192.168.100.38" :local_port => 44612 :path => "/v2.0/subnets" :port => 9696 :reason_phrase => "Bad Request" :remote_ip => "10.8.58.70" :status => 400 :status_line => "HTTP/1.1 400 Bad Request\r\n"  displayed in UI.

Expected results:
Flash messages needs to be improved

Additional info:

Comment 5 Gilles Dubreuil 2016-10-22 02:54:02 UTC
Ladislav,

Ok, I'll look at that.

Thanks

Comment 6 Gilles Dubreuil 2017-01-12 07:27:13 UTC
Ladislav, 

I believe this is irrelevant as we're now using the task queue approach to wrap all commands.

Do you agree?

Comment 7 Ladislav Smola 2017-01-12 08:50:56 UTC
I think so, you show just the message now, in case of the error, right?

Comment 8 Gilles Dubreuil 2017-01-24 08:58:44 UTC
Yes, the message is passed by from the task.

Therefore this bug becomes irrelevant and can be closed.


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