Status list "last check-in" not working?


#1

Maybe I don’t understand how it’s supposed to work, but a node with a
successful chef-client run isn’t supposed to count as a check-in?

On the node:

kom@nouvel~ $ tail -n100 /var/log/chef/client.log

[Thu, 25 Jun 2009 17:21:32 +0200] INFO: Starting Chef Run
[Thu, 25 Jun 2009 17:21:50 +0200] INFO: Updating file[/etc/inittab] with new
atime/mtime of Thu Jun 25 17:21:50 +0200 2009
[Thu, 25 Jun 2009 17:21:52 +0200] INFO: Chef Run complete in 19.216053
seconds

That’s 3mins ago.

In the interface:

http://files.getdropbox.com/u/31054/chef-status.png

It updated this morning when I updated chef to 0.7.2, but nothing after that

Thanks!

Albert Llop
Tech Department
albert@kingsofmambo.com


#2

On Thu, Jun 25, 2009 at 8:30 AM, Albert Llopmrsimo@gmail.com wrote:

Maybe I don’t understand how it’s supposed to work, but a node with a
successful chef-client run isn’t supposed to count as a check-in?

On the node:

kom@nouvel~ $ tail -n100 /var/log/chef/client.log

[Thu, 25 Jun 2009 17:21:32 +0200] INFO: Starting Chef Run
[Thu, 25 Jun 2009 17:21:50 +0200] INFO: Updating file[/etc/inittab] with new
atime/mtime of Thu Jun 25 17:21:50 +0200 2009
[Thu, 25 Jun 2009 17:21:52 +0200] INFO: Chef Run complete in 19.216053
seconds

That’s 3mins ago.

In the interface:

http://files.getdropbox.com/u/31054/chef-status.png

Smells like a bug! :slight_smile:

We’ll check it out.

Adam


Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-4759 E: adam@opscode.com