| 2023-03-14 09:21:41 |
Lukas Koenen |
description |
When sharing a security group using rbac policies
openstack network rbac create --target-project PROJECT_UUID --action \
access_as_shared --type security_group SEC_GROUP_UUID
the shared policy is not visible in the project it is shared to when using Horizon. Not in the security group overview and not when editing an instance. The only way to assign the shared security group is using the openstack cli (only UUIDs work). After assigning the shared security group is only visible in Horizon when inspecting the instance.
Furthermore when editing the assigned security groups of an instance using Horizon the shared security group (assigned via cli) gets removed automatically.
Steps to reproduce:
1. create security group
2. share security group
openstack network rbac create --target-project PROJECT_UUID --action \
access_as_shared --type security_group SEC_GROUP_UUID
3. assign security group
openstack server add security group INSTANCE_UUID SEC_GROUP_UUID |
When sharing a security group using rbac policies
openstack network rbac create --target-project PROJECT_UUID --action \
access_as_shared --type security_group SEC_GROUP_UUID
the shared policy is not visible in the project it is shared to when using Horizon. Not in the security group overview and not when editing an instance. The only way to assign the shared security group is using the openstack cli (only UUIDs work). After assigning the shared security group is only visible in Horizon when inspecting the instance.
Furthermore when editing the assigned security groups of an instance using Horizon the shared security group (assigned via cli) gets removed automatically.
Steps to reproduce:
1. create security group
2. share security group
openstack network rbac create --target-project PROJECT_UUID \
--action access_as_shared \
--type security_group SEC_GROUP_UUID
3. assign security group
openstack server add security group INSTANCE_UUID SEC_GROUP_UUID |
|
