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:
parent
c309df02a2
commit
84de58e02e
@ -11,6 +11,7 @@ class virtual_accelerator::config inherits virtual_accelerator {
|
|||||||
} ->
|
} ->
|
||||||
exec {'disable_apparmor':
|
exec {'disable_apparmor':
|
||||||
command => "apparmor_parser -R /etc/apparmor.d/usr.sbin.libvirtd",
|
command => "apparmor_parser -R /etc/apparmor.d/usr.sbin.libvirtd",
|
||||||
|
returns => [0, 254],
|
||||||
} ->
|
} ->
|
||||||
file { '/etc/init/cpu-cgroup.conf':
|
file { '/etc/init/cpu-cgroup.conf':
|
||||||
owner => 'root',
|
owner => 'root',
|
||||||
|
Loading…
Reference in New Issue
Block a user