openstack
/
charm-cinder
Code Issues Proposed changes

Re-enable AppArmor enforcement 

Ensure tests are run with aa-profile-mode=enforce. So we should be able
to notice any future behavioral changes in the upstream or additional
rules required for nova-compute AppArmor profile in the functional
tests.

func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/907

Related-Bug: #1979812
Related-Bug: #1939389

Change-Id: If658d9e8ee11248ef09e774f3e21fe0f801dc066
(cherry picked from commit ba21da64f6)
This commit is contained in:
Nobuto Murata 2022-07-07 09:37:28 +09:00
parent 2b71f3b1d7
commit aa96cb0efd
2 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
tests/bundles/focal-victoria.yaml
View File

@ -140,8 +140,7 @@ applications:
options:
config-flags: auto_assign_floating_ip=False
enable-live-migration: false
# disable apparmor because of https://bugs.launchpad.net/charm-nova-compute/+bug/1979812
# aa-profile-mode: enforce
aa-profile-mode: enforce
#ephemeral-device: /dev/vdb
#ephemeral-unmount: /mnt
debug: true

3
tests/bundles/focal-wallaby.yaml
View File

@ -140,8 +140,7 @@ applications:
options:
config-flags: auto_assign_floating_ip=False
enable-live-migration: false
# disable apparmor because of https://bugs.launchpad.net/charm-nova-compute/+bug/1979812
# aa-profile-mode: enforce
aa-profile-mode: enforce
#ephemeral-device: /dev/vdb
#ephemeral-unmount: /mnt
debug: true