Open quulah opened 7 years ago
The first two are easily fixed.
For the third, I moved the usage of dpkg_autostart to have :create before the installation is done.
For the fourth one, I added Chef version 12.20.3 to the .kitchen.yml files and also added the sentinel suite to the .kitchen.dokken.yml. I also changed the policies to have the run_lists separately, as it looked to me as the default recipe was always converged even though the sentinel one should be separate. But, I have not used Policyfiles before so that could be my fault too.
The fifth one was fixed by using the same template handling in redis_sentinel as the redis_instance already has.
And last, but not least, I added the --sentinel parameter for the process. Ubuntu / Debian also have a separate redis-sentinel package, but I think this is the easiest way. The sentinel_program parameter was also unused, but I left it there for now.
The configuration file has now writable permissions for the user. This is related to issue #18 too.
All this required a few changes to the sentinel control files, but now they're passing.
Installation of the Sentinel fails with the following errors. I have a pull request ready.
The sentinel.rb has a few errors:
Package installation fails atleast on Ubuntu 16.04, this affects the default recipe too.
Kitchen files have no version and the run_lists in the policies are a bit mixed.
The redis_sentinel resource has a broken template version handling.
Sentinel service parameters don't have --sentinel and the permissions of the file stop the service from starting.