yahoo-eng-team team mailing list archive

[Vahid Hashemian <vahidhashemian@xxxxxxxxxx>]

Public bug reported:

Security Groups each project after restacking is reported as 0 (default:
"Used 0 of 10") even though the "default" security group is the default
security group of each project. So it should report as 1 ("Used 1 of
10").

Steps to reproduce:
1. Restack
2. Login to Horizon
3. Go to Project > Overview panel
4. You'll notice that "Security Groups" are reported "0 of 10" -- which is incorrect
5. Now go to "Access & Security"
6. Go back to Overview
7. You'll notice that "Security Groups" are now reported "1 of 10" -- which is correct

NOTE: Neutron should not be enabled to reproduce this bug.

This bug is related to bug #1271381, which fixes the reported number for
most cases.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: nova project security-groups

** Summary changed:

- Incorrect number of security groups in Project Overview of restacking
+ Incorrect number of security groups in Project Overview after restacking

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1291048

Title:
  Incorrect number of security groups in Project Overview after
  restacking

Status in OpenStack Compute (Nova):
  New

Bug description:
  Security Groups each project after restacking is reported as 0
  (default: "Used 0 of 10") even though the "default" security group is
  the default security group of each project. So it should report as 1
  ("Used 1 of 10").

  Steps to reproduce:
  1. Restack
  2. Login to Horizon
  3. Go to Project > Overview panel
  4. You'll notice that "Security Groups" are reported "0 of 10" -- which is incorrect
  5. Now go to "Access & Security"
  6. Go back to Overview
  7. You'll notice that "Security Groups" are now reported "1 of 10" -- which is correct

  NOTE: Neutron should not be enabled to reproduce this bug.

  This bug is related to bug #1271381, which fixes the reported number
  for most cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1291048/+subscriptions