Fixes #8409 - Pull docker image asynchronously

[dLobatog]

No description provided.

[dLobatog]

This was changed so that when no Cmd is specified, it uses the default. Otherwise a .merge will not replace a [] as it's not nil.

[dLobatog]

I left this commented out while I was developing this feature - should NOT be commented normally

[dLobatog]

Updated to let the action be a good thread citizen and not block the pool. To be tested with foreman core develop, I'll submit a patch with 1.7 compat fixes separately so we can keep track of these.

cc @witlessbird @daviddavis @parthaa can you test it?

[pitr-ch]

This is not a thread save call, changing the state of the action from a different thread. The error needs to be sent back to the action same as :done event.

[dLobatog]

Updated with a test for the provision plan and commented out the tests for the run phase of start and pull. I'll work with @iNecas or @pitr-ch trying to figure out what I'm doing wrong so that these tests don't pass.

[domcleal]

re the test failure, what appears to be happening is that foreman-tasks is registering its extensions to the test rake task from its engine.rb initialisers. foreman-docker is of course requiring foreman-tasks, but the 'test' task(s) are now extended with both foreman-docker's and foreman-tasks' tests.

I don't know whether we should be running foreman-tasks' tests from here or not. We run core tests from plugins to check a plugin didn't break a core behaviour, and you could argue whether that should be the case or not for a plugin building on another plugin. It might be harder, since plugin tests may require additional development dependencies.

If you do want to run foreman-tasks tests, then I think something's wrong with the load paths (here?).

If not, then some refactoring of how rake tasks are modified (e.g. so they only happen when testing the plugin itself) or how we choose which sets are run is needed.. I need to think a bit more about that I guess.

[dLobatog]

This is lacking a test - and errors is not defined

[iNecas]

This PR should address the issue with the foremant-tasks tests (so that the tasks tests should not be run as part of this engine tests) theforeman/foreman-tasks#103

[dLobatog]

@iNecas Awesome! Any prospective dates for a release?

[iNecas]

Hopefully today, we have other feature that I would like to get in before the release, but if we don't get that done till tomorrow, i will release new version without it anyway.

[iNecas]

The new versions in a PR for foreman-packaging theforeman/foreman-packaging#582

[iNecas]

[test]

[dLobatog]

[test]

[dLobatog]

[test] this got aborted I think

[dLobatog]

[test] - tests were failing because I was using minitest-reporters here (and it's not used in Foreman core)

[dLobatog]

@daviddavis @parthaa @witlessbird Could you give a last test at this before merging?

[dmitri-d]

looks good to me.

[dLobatog]

I've been testing this a bit more thoroughly myself and I think this should:

• Show a link to the task created when creating a container, telling the user to check Monitor > Tasks is not very user friendly.
• If the task fails, show in the show container page that the task in question failed

I'll polish it up with these changes & resubmit when I get a chance.

[daviddavis]

@dLobatog any updates?

[dLobatog]

I'll pick this up again when ActiveJob is available