yahoo-eng-team team mailing list archive

[Alvaro Uria <1860685@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Running Ubuntu Bionic 18.04 + Queens.

= Reproducer
* log as "admin@admin_domain"
* have multiple projects. Each of them has the "default" security group (and may have other secgroups)
* Switch context to a project
* On an instance (from the "Project" section), go to edit security groups
* On the left column, multiple "default" security groups will exist and there is no way to know from which tenants they are.

= Suggestion
Change the shown name from "<secgroup-name>" to "<secgroup-name> (<tenant>)".

= Bug
If an instance from tenant1 has the "default" secgroup from the "admin" tenant, traffic will be affected (no matter the rules are the same).

Besides the above, the bug is that you don't know which "default"
secgroup is being added to an instance. From the console, there is the
option to use the secgroup_uuid.

** Affects: horizon
     Importance: Undecided
         Status: New

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

Title:
  "Edit security groups" for an instance shows multiple "default"
  security groups

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Running Ubuntu Bionic 18.04 + Queens.

  = Reproducer
  * log as "admin@admin_domain"
  * have multiple projects. Each of them has the "default" security group (and may have other secgroups)
  * Switch context to a project
  * On an instance (from the "Project" section), go to edit security groups
  * On the left column, multiple "default" security groups will exist and there is no way to know from which tenants they are.

  = Suggestion
  Change the shown name from "<secgroup-name>" to "<secgroup-name> (<tenant>)".

  = Bug
  If an instance from tenant1 has the "default" secgroup from the "admin" tenant, traffic will be affected (no matter the rules are the same).

  Besides the above, the bug is that you don't know which "default"
  secgroup is being added to an instance. From the console, there is the
  option to use the secgroup_uuid.

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