Description of problem:
In the Networks> Subnets view, for openstack provider subnets, the number of instances show one more than actual value. for example, if the number of instances is 2 for that subnet, it would show 3
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Go to Networks > Subnets
2. Notice the number of instances would be one more than the value shown in Networks > Networks
Number of instances shows 1 more than actual value
Number of instances should be shown accurately
To clarify the description of the issue, the number of subnets shown in CloudForms (Network -> Subnet) is more than the number of subnets visible in OpenStack. Is that correct?
Are undercloud (director - infra) and overcloud defined in CF? In which case any network and subnet defined in the undercloud are also added to the list of visible items in the Cloud Network and Cloud Subnet pages. So by default that makes +1 network and +1 subnet.
I confirm the total number of instances displayed in the "Cloud Subnet" summary page is wrong. The total has one more count than it should.
The right value is actually available on each subnet detail by clicking on a specific subnet. That could be used as a workaround for now.
This issue can be reproduced on master/HEAD branch where it would have to be fixed before being back ported to current version.
New commit detected on ManageIQ/manageiq/master:
Author: Keenan Brock <firstname.lastname@example.org>
AuthorDate: Mon Jul 9 16:41:51 2018 -0400
Commit: Keenan Brock <email@example.com>
CommitDate: Mon Jul 9 16:41:51 2018 -0400
Network Subnet total_vms work correctly
CloudSubnet#total_vms does not use distinct for the count
after: both use distinct (since it is going :through a has_many
app/models/cloud_subnet.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
That patch fixes the problems: https://github.com/ManageIQ/manageiq/pull/17683
Leaving as ON_DEV until a build is made
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.