[chef] Re: knife node changes and client run concurrency

[Adam Jacob < >]

Every object in chef is last-writer-wins. There is, at this time, no way
to guard against this.

Adam

On 3/8/13 12:25 AM, "Martin Eigenbrodt" 
<
 >
 wrote:

>Hi there,
>
>i experienced the following problem: A CI Job ran "knife node from file
>.." but the node attributes seemed to be unchanged later. Investigating
>erchefs Log I found out, that there had been an concurrent chef-client
>run on the relevant node.
>It looks like the client read the node data before the run, while it run
>knife has updated the data and after the run the client pushed  its old
>node - and know wrong - data back to the server.
>
>Is this a known issue? How can I guard against this?
>
>
>Regards,
>
>Martin