[Ovirt-devel] [PATCH server] make dnsmasq start earlier on boot otherwise dbomatic/taskomatic fail due to timeouts

[Joey Boggs]

----- Original Message -----
From: "Jeremy Katz" <katzj at redhat.com>
To: ovirt-devel at redhat.com
Sent: Monday, February 16, 2009 11:31:35 AM GMT -05:00 US/Canada Eastern
Subject: Re: [Ovirt-devel] [PATCH server] make dnsmasq start earlier on boot otherwise dbomatic/taskomatic fail due to timeouts

On Friday, February 13 2009, Joey Boggs said:
> ---
>  installer/modules/ovirt/manifests/dns.pp |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/installer/modules/ovirt/manifests/dns.pp b/installer/modules/ovirt/manifests/dns.pp
> index cbe706a..8fb8045 100644
> --- a/installer/modules/ovirt/manifests/dns.pp
> +++ b/installer/modules/ovirt/manifests/dns.pp
> @@ -66,6 +66,10 @@ define dns::common($mgmt_ipaddr="", $prov_ipaddr="",$mgmt_dev="",$prov_dev="") {
>          notify => Service[dnsmasq],
>      }
>  
> +    single_exec {"make_dnsmasq_start_earlier":
> +        command => "/bin/mv /etc/rc3.d/S99dnsmasq /etc/rc3.d/S95dnsmasq;/bin/mv /etc/rc5.d/S99dnsmasq /etc/rc5.d/S95dnsmasq",
> +        require => Package["dnsmasq"]
> +    }
>  }

This is going to break in any circumstance that the dnsmasq package is
upgraded or chkconfig is re-run for various reasons.  This really needs
to be fixed by changing the initscript in the package and not by moving
symlinks around.  

Although, actually, it looks like there's also some support in chkconfig
for override files -- read the bit on override files and chkconfig
--override in chkconfig(8) to give a short-term solution until the
package is changed

Jeremy


______________________________________________
Ovirt-devel mailing list
Ovirt-devel at redhat.com
https://www.redhat.com/mailman/listinfo/ovirt-devel



I figured that the upgrade path wouldn't affect the chkconfig, my first solution was to edit the chkconfig information like you mentioned but, using puppet I would have to perform a few things manually seemingly overkill, rather than be able to use the built in service resource. In the case of an dnsmasq upgrade wouldn't the init script be replaced as well since it's not marked as a config file?