[chef] Re: chef-client -o changing run_list on chef server

[Chris Roberts < >]

Hi,

Not expected and addressed here: http://tickets.opscode.com/browse/CHEF-3167


Motiejus Jakštys writes:

> Hi,
>
> I don't know if this is expected behavior, but specifying -o
> recipe[chef-client] when running chef-client removes current run list
> from a node.
>
> Before chef-client -o recipe[chef-client] invocation:
>
> $ knife node show node.gla.ac.uk
> Node Name:   node.gla.ac.uk
> Environment: _default
> FQDN:        node.gla.ac.uk
> IP:          10.199.198.15
> Run List:    role[debian]
> Roles:       debian
> Recipes:     apt, apt::cacher-client, packages, ntp, chef-client,
> users::sysadmins, sudo, ssmtp, resolver, fail2ban
> Platform:    debian 6.0.5
>
> After:
> Node Name:   node.gla.ac.uk
> Environment: _default
> FQDN:        node.gla.ac.uk
> IP:          10.199.198.15
> Run List:    recipe[chef-client]
> Roles:
> Recipes:     chef-client
> Platform:    debian 6.0.5
>
> Is this expected behavior?
>
> My plan is to execute chef-client first on first boot, and then let it
> proceed with other (possibly buggy) recipes when the VM is installed
> properly (and hence can restart chef-client when the recipes are
> fixed).
>
> Using chef 0.10.10 on VM and chef server.
>
> Thanks,
> Motiejus Jakštys