Red Hat Bugzilla – Bug 1479667
Azure Cloud Network cfmeautopay shows higher instances number
Last modified: 2018-03-01 08:15:53 EST
Description of problem: In summary of "cfmeautopay" cloud network of azure Network Manager is the number of Relationships->Instances 10. After redirection by clicking on Relationships->Instances are shown only 9. Version-Release number of selected component (if applicable): 5.8.1.5 downstream-58z How reproducible: Randomly Steps to Reproduce: 1. Add Azure Cloud Network Provider 2. Navigate to Networks->Networks->cfmeautopay 3. Check the Relationships->Instances number 4. Click on Relationships->Instances 5. Check the number of shown instances Actual results: 1. Numbers in step 3 and step 5 are different. 2. Numbers in step 3 is different than the number of VMs connected to cfmeautopay Cloud Networks in Networks->Topology Expected results: 1. Numbers in step 3 and step 5 should not differ. 2. Numbers in step 3 should be equal with number of VMs connected to cfmeautopay Cloud Networks in Networks->Topology Additional info: Problem may to connected to the number of ports of instances. Only one instance has 2 ports instead of 1, which may cause the higher number of instances in the summary
https://github.com/ManageIQ/manageiq/pull/15783
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/77a77d710e7271d92b8b865a3fcb2d46cb27ea8d commit 77a77d710e7271d92b8b865a3fcb2d46cb27ea8d Author: Ladislav Smola <lsmola@redhat.com> AuthorDate: Thu Aug 10 11:20:11 2017 +0200 Commit: Ladislav Smola <lsmola@redhat.com> CommitDate: Thu Aug 10 11:20:11 2017 +0200 Make networks vms relations distinct Make networks vms relations distinct, otherwise the Vm count could be shown as higher, if the the vm has multiple ports plugged into the same network. Fixes BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1479667 app/models/cloud_network.rb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
Sorry, accidentally changed state.
Tested on version 5.9.0.5 -> Azure. Tests passed.
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:0380