| 2023-09-26 20:10:35 |
Jake Nabasny |
bug |
|
|
added bug |
| 2023-09-26 20:48:19 |
Alex Kavanagh |
charm-openstack-dashboard: status |
New |
Incomplete |
|
| 2023-09-27 07:44:59 |
Marcin Wilk |
bug |
|
|
added subscriber Marcin Wilk |
| 2023-12-04 04:17:18 |
Launchpad Janitor |
charm-openstack-dashboard: status |
Incomplete |
Expired |
|
| 2024-01-05 16:59:06 |
Jake Nabasny |
description |
== ENVIRONMENT ==
OS: Ubuntu Focal and Jammy
Openstack: Ussuri and Yoga
Charm revision: 585 and 597
== ISSUE ==
The first time adding a policy override file and enabling policy overrides, they get applied as expected. But if you upload another policy override zip file, you need to make a charm configuration change, like disabling and re-enabling policy overrides, in order for the new policies to be loaded.
== EXPECTED OUTCOME ==
New policy overrides are applied at the time when the override file is attached to the charm.
== STEPS TO REPRODUCE ==
On a fresh deployment:
1. mkdir compute && echo '"os_compute_api:os-extended-server-attributes": "rule:admin_or_owner"' > compute/attribute-override.yaml
2. zip -r nova-override.zip compute
3. juju attach-resource keystone policyd-override=nova-override.zip
4. juju config openstack-dashboard use-policyd-override=true
# Policies applied as expected, then adding another policy:
5. mkdir identity && echo '"admin_required": "role:Admin or role:cloudadmin"' > identity/admin-override.yaml
6. zip -r keystone-override.zip identity
7. juju attach-resource keystone policyd-override=keystone-override.zip
# Charm goes into maintenance mode and regenerates endpoint configs, but the change does not take effect.
8. juju config openstack-dashboard use-policyd-override=false
9. juju config openstack-dashboard use-policyd-override=true
# Now the newly added policy gets applied.
== OTHER NOTES ==
After step 7, there is no directory for /etc/openstack-dashboard/policy.d/keystone_policy.d/. It does not get generated until the workaround is applied with steps 8 and 9. |
== ENVIRONMENT ==
OS: Ubuntu Focal and Jammy
Openstack: Ussuri and Yoga
Charm revision: 585 and 597
== ISSUE ==
The first time adding a policy override file and enabling policy overrides, they get applied as expected. But if you upload another policy override zip file, you need to make a charm configuration change, like disabling and re-enabling policy overrides, in order for the new policies to be loaded.
== EXPECTED OUTCOME ==
New policy overrides are applied at the time when the override file is attached to the charm.
== STEPS TO REPRODUCE ==
On a fresh deployment:
1. mkdir compute && echo '"os_compute_api:os-extended-server-attributes": "rule:admin_or_owner"' > compute/attribute-override.yaml
2. zip -r nova-override.zip compute
3. juju attach-resource openstack-dashboard policyd-override=nova-override.zip
4. juju config openstack-dashboard use-policyd-override=true
# Policies applied as expected, then adding another policy:
5. mkdir identity && echo '"admin_required": "role:Admin or role:cloudadmin"' > identity/admin-override.yaml
6. zip -r keystone-override.zip identity
7. juju attach-resource openstack-dashboard policyd-override=keystone-override.zip
# Charm goes into maintenance mode and regenerates endpoint configs, but the change does not take effect.
8. juju config openstack-dashboard use-policyd-override=false
9. juju config openstack-dashboard use-policyd-override=true
# Now the newly added policy gets applied.
== OTHER NOTES ==
After step 7, there is no directory for /etc/openstack-dashboard/policy.d/keystone_policy.d/. It does not get generated until the workaround is applied with steps 8 and 9. |
|
| 2024-01-05 17:11:38 |
Jake Nabasny |
charm-openstack-dashboard: status |
Expired |
New |
|
| 2024-01-05 17:13:47 |
Jake Nabasny |
description |
== ENVIRONMENT ==
OS: Ubuntu Focal and Jammy
Openstack: Ussuri and Yoga
Charm revision: 585 and 597
== ISSUE ==
The first time adding a policy override file and enabling policy overrides, they get applied as expected. But if you upload another policy override zip file, you need to make a charm configuration change, like disabling and re-enabling policy overrides, in order for the new policies to be loaded.
== EXPECTED OUTCOME ==
New policy overrides are applied at the time when the override file is attached to the charm.
== STEPS TO REPRODUCE ==
On a fresh deployment:
1. mkdir compute && echo '"os_compute_api:os-extended-server-attributes": "rule:admin_or_owner"' > compute/attribute-override.yaml
2. zip -r nova-override.zip compute
3. juju attach-resource openstack-dashboard policyd-override=nova-override.zip
4. juju config openstack-dashboard use-policyd-override=true
# Policies applied as expected, then adding another policy:
5. mkdir identity && echo '"admin_required": "role:Admin or role:cloudadmin"' > identity/admin-override.yaml
6. zip -r keystone-override.zip identity
7. juju attach-resource openstack-dashboard policyd-override=keystone-override.zip
# Charm goes into maintenance mode and regenerates endpoint configs, but the change does not take effect.
8. juju config openstack-dashboard use-policyd-override=false
9. juju config openstack-dashboard use-policyd-override=true
# Now the newly added policy gets applied.
== OTHER NOTES ==
After step 7, there is no directory for /etc/openstack-dashboard/policy.d/keystone_policy.d/. It does not get generated until the workaround is applied with steps 8 and 9. |
== ENVIRONMENT ==
OS: Ubuntu Focal and Jammy
Openstack: Ussuri and Yoga
Charm revision: 585 and 597
== ISSUE ==
The first time adding a policy override file and enabling policy overrides, they get applied as expected. But if you upload another policy override zip file, you need to make a charm configuration change, like disabling and re-enabling policy overrides, in order for the new policies to be loaded.
== EXPECTED OUTCOME ==
New policy overrides are applied at the time when the override file is attached to the charm.
== STEPS TO REPRODUCE ==
On a fresh deployment:
1. mkdir compute && echo '"os_compute_api:os-extended-server-attributes": "rule:admin_or_owner"' > compute/attribute-override.yaml
2. zip -r nova-override.zip compute
3. juju attach-resource openstack-dashboard policyd-override=nova-override.zip
4. juju config openstack-dashboard use-policyd-override=true
# Policies applied as expected, then adding another policy:
5. mkdir identity && echo '"admin_required": "role:Admin or role:cloudadmin"' > identity/admin-override.yaml
6. zip -r nova-keystone-overrides.zip identity compute
7. juju attach-resource openstack-dashboard policyd-override=nova-keystone-overrides.zip
# Charm goes into maintenance mode and regenerates endpoint configs, but the change does not take effect.
8. juju config openstack-dashboard use-policyd-override=false
9. juju config openstack-dashboard use-policyd-override=true
# Now the newly added policy gets applied.
== OTHER NOTES ==
After step 7, there is no directory for /etc/openstack-dashboard/policy.d/keystone_policy.d/. It does not get generated until the workaround is applied with steps 8 and 9. |
|
| 2024-01-08 15:01:21 |
Alex Kavanagh |
charm-openstack-dashboard: status |
New |
Incomplete |
|
| 2024-03-09 04:17:11 |
Launchpad Janitor |
charm-openstack-dashboard: status |
Incomplete |
Expired |
|
| 2024-03-09 17:11:44 |
Alex Kavanagh |
charm-openstack-dashboard: status |
Expired |
Incomplete |
|
| 2024-05-09 04:17:16 |
Launchpad Janitor |
charm-openstack-dashboard: status |
Incomplete |
Expired |
|
