devtest.sh run leaves 3 default security groups

[Gavin B]

After a run of devtest.sh. you find that there are 3 default security groups :

e.g.

(tempest)root@overcloud-notcompute0-zeb6ebhvusrs:/opt/stack/tempest# neutron security-group-list
+--------------------------------------+---------+-------------+
| id | name | description |
+--------------------------------------+---------+-------------+
| 1a29a961-4331-4022-87d5-d6432127d750 | default | default |
| c6e2198b-cc6a-4992-84dd-00fb6753be59 | default | default |
| fc932556-70fe-4e8c-b708-1588b38907f2 | default | default |
+--------------------------------------+---------+-------------+

While not a major problem, it does get in the way, and should be tidied up.

[Roman Podoliaka (rpodolyaka)]

Just checked my overcloud. Indeed, there are 3 different security groups, one per tenant (admin, service, demo).

neutron security-group-list run from admin user indeed prints 3 sec groups with the same name, but those are, in fact, 3 different security groups.

Could you please elaborate when this can be a problem? So we could decide, if it's a TripleO or Neutron bug? Perhaps, it's not a bug at all: when user credentials are used, only one security group 'default' is returned. Marking this as incomplete for now.

[Gavin B (gavin-brebner-orange)]

It certainly can create confusion.

Perhaps rather than calling them all "default" the admin and service groups could be called
admin-default and service-default or something ?

This is borderline given that switching to user creds gets you into a "normal" environment.

[Robert Collins (lifeless)]

SO, if there is a bug here, it is neutron security-group-list showing groups for other tenants by default. I'm going to retarget this to neutron.

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]