Puppet users - Jan 2007 - Inconsistent notices during puppetd --test run

I added ntp to my servers running with puppet. These are all Ubuntu
machines, btw.

I get the following in the verbose output:
{{{

warning: Service[ntp-server](provider=debian): Could not start
Service[ntp-server]: Execution of ''/etc/init.d/ntp-server
start''
returned 256:  * Starting NTP server...

notice: /base/Service[ntp-server]/ensure: ensure changed
''stopped'' to ''running''

}}}

So, it first says it failed to start the service, and then says the
service changed from stopped to running. And indeed, the service start
successfully.

I have also noticed that I get quite few notices like the following:
{{{

notice: Package[xxx](provider=apt): Failed to handle dpkg-query line
"unknown ok not-installed xxx "

}}}

I think possibly the first problem is related to a different
start/stop script in Ubuntu than in Debian, maybe?
Dunno if the second is a problem, as the packages do seem to install.

Thijs

On Tue, Jan 23, 2007 at 06:21:43PM +0100, Thijs Oppermann
wrote:
> I added ntp to my servers running with puppet. These are all Ubuntu
> machines, btw.
> 
> I get the following in the verbose output:
> {{{
> 
> warning: Service[ntp-server](provider=debian): Could not start
> Service[ntp-server]: Execution of ''/etc/init.d/ntp-server
start''
> returned 256:  * Starting NTP server...
If your init script will return funky values... <grin>
> notice: /base/Service[ntp-server]/ensure: ensure changed
''stopped'' to ''running''
> 
> }}}
> 
> So, it first says it failed to start the service, and then says the
> service changed from stopped to running. And indeed, the service start
> successfully.
That seems a bit... fruity.  I haven''t looked at the services code at
all,
but I''d imagine that the ''ensure'' state probably does
something to work out
whether the state change actually occured, and since, as you say, the NTP
daemon did actually start successfully, the service probably considers that
everything went quite swimmingly.  The core problem there, I think, is that
the ntp-server init script is returning non-zero when it probably
shouldn''t
be.
> I have also noticed that I get quite few notices like the following:
> {{{
> 
> notice: Package[xxx](provider=apt): Failed to handle dpkg-query line
> "unknown ok not-installed xxx "
That''s a straight-up bug, that has been fixed for the next release.  As
you
say, it''s largely cosmetic, as the packages do get installed
successfully.

- Matt

On Jan 23, 2007, at 11:21 AM, Thijs Oppermann wrote:
> I added ntp to my servers running with puppet. These are all Ubuntu
> machines, btw.
>
> I get the following in the verbose output:
> {{{
>
> warning: Service[ntp-server](provider=debian): Could not start
> Service[ntp-server]: Execution of ''/etc/init.d/ntp-server
start''
> returned 256:  * Starting NTP server...
>
> notice: /base/Service[ntp-server]/ensure: ensure changed
''stopped''
> to ''running''
>
> }}}
>
> So, it first says it failed to start the service, and then says the
> service changed from stopped to running. And indeed, the service start
> successfully.
Filed as #454.

  --
  The great tragedy of Science - the slaying of a beautiful  
hypothesis by
  an ugly fact.   --Thomas H. Huxley
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com