2017-05-03 16:08:56 +02:00
|
|
|
class openstack_integration::redis {
|
|
|
|
include ::openstack_integration::config
|
|
|
|
|
2018-06-01 08:08:30 -06:00
|
|
|
# due to issues in OpenStack CI with the redis package, we need to disable
|
|
|
|
# the service enable flag. The service still starts but the management of
|
|
|
|
# the service with systemd errors.
|
|
|
|
if ($::os_package_type == 'debian') {
|
|
|
|
$service_enable = false
|
|
|
|
} else {
|
|
|
|
$service_enable = true
|
|
|
|
}
|
|
|
|
|
2017-05-03 16:08:56 +02:00
|
|
|
class { '::redis':
|
Debian: fix redis service setup
The redis-server appears as "masked" in the OpenStack CI, even though it
did not in my test VM. As a consequence, "systemctl enable redis-server"
fails, and consequently, the puppet run fails in OpenStack CI. The thing
is, there's no need to enable this service, as in all distros, it's
already enabled by default. Even in the OpenStack CI, the service appears
as enabled, but masked (which by the way, should never happen, as this
isn't a working systemd state).
This patch simply removes the enabling of the systemd service, so that
it also works in Debian in the CI.
Change-Id: I1b37524ff1071d87e8a7df2fa3bca66aed162d1b
2018-05-31 21:24:10 +02:00
|
|
|
bind => $::openstack_integration::config::host,
|
2018-06-01 08:08:30 -06:00
|
|
|
service_enable => $service_enable
|
2017-05-03 16:08:56 +02:00
|
|
|
}
|
|
|
|
}
|