[Ovirt-devel] [PATCH server] fix the ovirt-mongrel-rails restart problem in the installer if ran more than once
Joey Boggs
jboggs at redhat.com
Mon Apr 27 18:00:49 UTC 2009
Due to the service name not matching the actual process name, puppet thinks that ovirt-mongrel-rails is never running and tries to start it everytime the installer runs, this adds the hasstatus option to use a service status check rather than puppet's process grep method.
---
installer/modules/ovirt/manifests/ovirt.pp | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/installer/modules/ovirt/manifests/ovirt.pp b/installer/modules/ovirt/manifests/ovirt.pp
index 09b1925..03a93a7 100644
--- a/installer/modules/ovirt/manifests/ovirt.pp
+++ b/installer/modules/ovirt/manifests/ovirt.pp
@@ -156,7 +156,8 @@ class ovirt::setup {
enable => true,
require => [Package[ovirt-server],Single_Exec[db_migrate]],
ensure => running,
- notify => Service[httpd]
+ notify => Service[httpd],
+ hasstatus => true
}
service {"ovirt-taskomatic" :
--
1.6.0.6
More information about the ovirt-devel
mailing list