Bug 1392008 - Can't associate floating IP with OpenStack instance
Summary: Can't associate floating IP with OpenStack instance
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: GA
: 5.8.0
Assignee: Tzu-Mainn Chen
QA Contact: Ola Pavlenko
URL:
Whiteboard:
Depends On:
Blocks: 1393518
TreeView+ depends on / blocked
 
Reported: 2016-11-04 15:02 UTC by Oleksandr Kolisnyk
Modified: 2017-08-30 03:50 UTC (History)
8 users (show)

Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1393518 (view as bug list)
Environment:
Last Closed: 2017-06-12 16:08:30 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Error msg screen (114.54 KB, image/png)
2016-11-04 15:02 UTC, Oleksandr Kolisnyk 		no flags Details
View All

Description Oleksandr Kolisnyk 2016-11-04 15:02:31 UTC 
Created attachment 1217419 [details]
Error msg screen

How reproducible:
Always

Setup:
CFME 5.7 + RHOS 10 (as Cloud provider), at least one OpenStack instance running, one free floating IP available

Steps to Reproduce:
1. Login to CF UI
2. Go Compute -> Cloud -> Instances
3. Click on your instance
4. On the instance page, go Configuration -> Associate a Floating IP with this instance
5. Select one of the items from "Floating IP" list
6. Click on "Submit" button

Actual results:
Redirection to "Instances" page with the message "Unable to associate Floating IP 1000000000001 with Instance "test": Invalid input for field/attribute address. Value: 1000000000001. u'1000000000001' is not valid under any of the given schemas"

Expected results:
Message says "Associating of floating IP was successfully initiated"

Additional info:
Got the same error for disassociating operation
Comment 2 Sam Lucidi 2016-11-04 18:16:29 UTC 
A pull request to address this issue is up: https://github.com/ManageIQ/manageiq/pull/12446
Note You need to log in before you can comment on or make changes to this bug.