Closed jschaeff closed 6 years ago
@jschaeff is it still the case with latest version of the module ?
Yes, it's still the case. I forced the ordering by adding the dependency :
--- a/manifests/openmanage/debian.pp +++ b/manifests/openmanage/debian.pp @@ -212,4 +212,6 @@ SNnmxzdpR6pYJGbEDdFyZFe5xHRWSlrC3WTbzg== before => Service['dataeng'], }
I merged https://github.com/camptocamp/puppet-dell/pull/45. Does it fix it?
tag 0.1.1 still has ordering issues.
It's trying to start dataeng before the package is installed. Then after trying to start the service, it then tries to install the package that contains the service. Then after trying to install the package, it then tried to add the repo from which to install.
Ultimately, it should progress as this:
repo -> package -> service
whereas right now it flows:
service -> package -> repo.
(trying on ubuntu 14.04)
@stumped2 @jschaeff does https://github.com/camptocamp/puppet-dell/pull/50 fix it?
@raphink I just finished getting test-kitchen + puppet set up, I'll test out #50 and let you know.
EDIT: commented on the PR.
Cool. How does test-kitchen+puppet compare with beaker?
@raphink I originally started out my SysAdmin days using chef, so I am sort of biased towards test-kitchen since it was such a great tool in the chef world.
For the most part, test kitchen + puppet is great, if you don't want to do advanced/weird things since the puppet provisioner docs are sorely lacking.
I did a quick glance at beaker, and it looks cool, but it would take a bit for me to convert over to beaker setup from test kitchen.
What are the advantages of test-kitchen?
In what aspect do you mean?
The dell::hwtools class needs the configuration of the package repository wich will only be setup afterwards (in dell::openmanage).
The ordering does not seem straightforward to describe because the 2 classes should stay "independent" ...