first install with plugins fails

[bkw]

I'm using the normal tar installation.
I'm starting off from a naked system (no /usr/local/elasticsearch* present).
I'm using the latest elasticsearch-recipe from github and the latest release of ark (0.3.2).

Everything runs smoothly, when I don't have plugins installed. I can also add plugins later, after the first chef run was successful. But this is not the point.

When I include plugins to be installed on the first chef run, the following happens:
The install recipe uses ark to download the tarball. The ark installer schedules execute[unpack] via a delayed notify.That notify is only being run at the end of the chef run.

In the meantime the elasticsearch::plugins recipe wants to install a plugin. It needs /usr/local/elasticsearch/bin/plugin for that, which does not exist yet, since the unpacking of the tarball has been delayed until the very end of the chef run.
So the plugin install fails, causing the whole chef-run to abort. This also prevents the delayed unpack action to ever be run, and the scenario repeats on the next chef run.

Sorry, no testcase, I wanted to get this out here as soon as possible; I lost a lot of hair over this.

[karmi]

Hmm, this is frustrating, and surprising as well -- the Vagrant-based tests include installation of plugins on the first run and they pass. Could you run those? (See README.)

[bkw]

confirmed that the vagrant tests run ok. Seems my analysis was wrong. I'll try to reproduce this.

[karmi]

@brwe Great!, will close the issue for now, if that's OK? Please ping me if you run into the issue again so we can reopen it.

[timechanter]

This is occuring here as well and is rather anoying. Could it be the ark version?

[bkw]

I haven't had the time to confirm this yet, but I'd rather suspect a difference between chef-solo and server. @timechanter did you use chef-solo or a chef-server?

[timechanter]

Its a chef-server 10 . I've seen the same issue on one of my own recipes , ever since the awk version made a major change to use Notifies. I ended up using two blocks and having the real dependency use a :delayed notify as well. Potentially chef 11 has slightly different behaviour?