When updating versions, the wrong version can be installed unless you manually clear node attributes (chef server only) about elasticsearch HOT 6 CLOSED

Hi, there's been a report like that in #61. I usually test the cookbook with Chef Solo in Vagrant and EC2, and don't have any streamlined workflow for Chef server -- looks like it's really needed.

My bet here is that Chef is failing to update attributes properly somehow. Could you run Chef with the debug or put require 'pry'; binding.pry and manually verify the download_url and other attributes? Also notice the fixed Chef behaviour in the 11 version [#68]

from elasticsearch.

See the info in #68, verified to work correctly on Chef 11.

from elasticsearch.

I was able to verify the latest code + chef 11 (client) resolves this issue. See #68 for details.

from elasticsearch.

So let's close this and continue in #68?

from elasticsearch.

So let's close this and continue in #68?

Sounds good. Closed.

from elasticsearch.

Extensively tested in Chef Solo and Chef Server in both Vagrant and EC2 machines, it should behave properly now with attributes set either in data bag, role, environment or directly on the node. Could you verify it, please?

from elasticsearch.