Bug 1393518 - Can't associate floating IP with OpenStack instance
Summary: Can't associate floating IP with OpenStack instance
Keywords:
Status: CLOSED ERRATA
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.7.0
Assignee: Tzu-Mainn Chen
QA Contact: Ola Pavlenko
URL:
Whiteboard: openstack:sdn
Depends On: 1392008
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-09 18:07 UTC by Satoe Imaishi
Modified: 2017-08-30 03:50 UTC (History)
10 users (show)

Fixed In Version: 5.7.0.11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1392008
Environment:
Last Closed: 2017-01-04 13:21:46 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0012 0 normal SHIPPED_LIVE CFME 5.7.0 bug fixes and enhancement update 2017-01-04 17:50:36 UTC

Comment 2 CFME Bot 2016-11-09 22:56:11 UTC 
New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/b7685a561bd39d52d2973df7c0182975d16a0d1f

commit b7685a561bd39d52d2973df7c0182975d16a0d1f
Author:     Martin Hradil <himdel>
AuthorDate: Wed Nov 9 13:50:23 2016 +0200
Commit:     Oleg Barenboim <chessbyte>
CommitDate: Wed Nov 9 17:55:24 2016 -0500

    Merge pull request #12446 from mansam/fix-floating-ip-select-box
    
    Make sure floating IP select box values are tracked by address, not id
    (cherry picked from commit 36f0e8ba1159ea095c4ae83f5541965cb98df09a)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1393518

 app/views/vm_common/_associate_floating_ip.html.haml    | 2 +-
 app/views/vm_common/_disassociate_floating_ip.html.haml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
Comment 3 Ronnie Rasouli 2016-11-20 09:58:06 UTC 
verified 5.7.0.10
Comment 5 errata-xmlrpc 2017-01-04 13:21:46 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0012.html
Note You need to log in before you can comment on or make changes to this bug.