75f55d13ad
The apparmor_parser actually doesn't remove the file or doesn't create the symlink in '/etc/apparmor.d/disable' itself so the next run of the baremetal role will fail with the error "Unable to remove "libvirtd". Even more after reboot, the profile is still active. We need to disable the profile completly ourselves. This change fixes the idempotents of the baremetal role. Closes-Bug: #1960302 Change-Id: I162e417387393e806886b1c9ea8053b89778b4d1 Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
8 lines
259 B
YAML
8 lines
259 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes the baremetal role to avoid an error "Unable to remove "libvirtd".
|
|
Now the symlink /etc/apparmor.d/disable/usr.sbin.libvirtd is created by
|
|
the role.
|
|
`LP#1960302 <https://bugs.launchpad.net/kolla-ansible/+bug/1960302>`__
|