6wind-virtual-accelerator-plugin: update apparmor exit status

When redeploying environments it may be possible that Linux
apparmor has already been configured (by a previous Fuel deployment
with the plugin).
In this case the apparmor command will fail since the configuration
it tries to enforce is already present (254 is returned as exit code).
This patch adds this exit code to the list of correct values in
the specific puppet exec.

Signed-off-by: Francesco Santoro <francesco.santoro@6wind.com>

Change-Id: I21617eee0a17b1e52b1f00f8a9905e4ad0b1a61e
This commit is contained in:
Francesco Santoro 2016-04-15 13:55:18 +02:00
parent c309df02a2
commit 84de58e02e
1 changed files with 1 additions and 0 deletions

View File

@ -11,6 +11,7 @@ class virtual_accelerator::config inherits virtual_accelerator {
} ->
exec {'disable_apparmor':
command => "apparmor_parser -R /etc/apparmor.d/usr.sbin.libvirtd",
returns => [0, 254],
} ->
file { '/etc/init/cpu-cgroup.conf':
owner => 'root',