They should and they *do* become active after hard reset, *unless* the corresponding apparmor profiles are empty after reboot (if FS cache buffers *are not* flushed to disks in time).
^ this should help make sure apparmor profiles content is synced to disks early or simply recreated on node boot if they still happen to be empty.
On the other hand, you should understand, that the very same thing happens to VMs disks: if the host node is accidentally reset, then some content may be missing on VMs start. You should account for that.
Timur,
They should and they *do* become active after hard reset, *unless* the corresponding apparmor profiles are empty after reboot (if FS cache buffers *are not* flushed to disks in time).
I've prepared a patch for libvirt here:
https:/ /review. fuel-infra. org/#/c/ 24954/
you can give the built packages a try:
http:// perestroika- repo-tst. infra.mirantis. net/review/ CR-24954/ mos-repos/ xenial/ master/
^ this should help make sure apparmor profiles content is synced to disks early or simply recreated on node boot if they still happen to be empty.
On the other hand, you should understand, that the very same thing happens to VMs disks: if the host node is accidentally reset, then some content may be missing on VMs start. You should account for that.