New commit detected on ManageIQ/manageiq-ui-classic/gaprindashvili: https://github.com/ManageIQ/manageiq-ui-classic/commit/76a3e1def7cd2dbbce6e2e75ea23ba68b601448f commit 76a3e1def7cd2dbbce6e2e75ea23ba68b601448f Author: Milan Zázrivec <mzazrivec> AuthorDate: Fri Jul 27 02:57:15 2018 -0400 Commit: Milan Zázrivec <mzazrivec> CommitDate: Fri Jul 27 02:57:15 2018 -0400 Merge pull request #4357 from gildub/no-allocated-IPs VM: associate only unused floating IPs (cherry picked from commit d777b49c83cb27bb288d80f227f71cdbf520beb9) https://bugzilla.redhat.com/show_bug.cgi?id=1623562 app/controllers/mixins/actions/vm_actions/associate_floating_ip.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Failed QA ========= CFME 5.9.5.0 While trying to associate FIP to an instance, no FIP listed. Only 'undefined' Screenshot is enclosed
Created attachment 1494059 [details] undefined
I confirm the list of floating IPs is not displaying properly. Investigating.
Upstream complementary patch has been merged. Waiting for backport to gaprindashvili.
New commit detected on ManageIQ/manageiq-ui-classic/gaprindashvili: https://github.com/ManageIQ/manageiq-ui-classic/commit/075812394abf5137e6c92f70b4fc3ac40b157c21 commit 075812394abf5137e6c92f70b4fc3ac40b157c21 Author: Milan Zázrivec <mzazrivec> AuthorDate: Tue Nov 20 06:37:41 2018 -0500 Commit: Milan Zázrivec <mzazrivec> CommitDate: Tue Nov 20 06:37:41 2018 -0500 Merge pull request #4944 from gildub/vm_cloud_floating_ip VM CLoud: floating ips to associate must be a list (cherry picked from commit 911a289574b1d433c6a8fcde890ebb39d7f24da2) https://bugzilla.redhat.com/show_bug.cgi?id=1623562 app/controllers/mixins/actions/vm_actions/associate_floating_ip.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Verified at CFME 5.9.6.5
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://access.redhat.com/errata/RHSA-2018:3816