DescriptionTakashi Kajinami
2020-04-13 02:22:05 UTC
Description of problem:
In RHOSP16.0, legacy Telemetry services (ceilometer, gnocchi and panko) are no more deployed by default.
However, we still see Redis is enabled by default, though there are no components using it.
~~~
[heat-admin@controller-0 ~]$ sudo pcs status
...
Full list of resources:
...
Container bundle set: redis-bundle [cluster.common.tag/rhosp16-openstack-redis:pcmklatest]
redis-bundle-0 (ocf::heartbeat:redis): Slave controller-0
redis-bundle-1 (ocf::heartbeat:redis): Master controller-1
redis-bundle-2 (ocf::heartbeat:redis): Slave controller-2
...
ip-172.17.1.85 (ocf::heartbeat:IPaddr2): Started controller-2
~~~
~~~
$ sudo podman ps | egrep -e ceilometer -e gnocchi -e aodh -e redis
525342a3909c undercloud-0.ctlplane.redhat.local:8787/rh-osbs/rhosp16-openstack-redis:20200226.1 /bin/bash /usr/lo... 6 minutes ago Up 6 minutes ago redis-bundle-podman-0
~~~
/var/lib/config-data/puppet-generated/haproxy/etc/haproxy/haproxy.cfg
~~~
listen redis
bind 172.17.1.85:6379 transparent
balance first
~~~
~~~
/var/lib/config-data/puppet-generated/redis/etc/redis.conf.puppet:dir /var/lib/redis
[heat-admin@controller-0 ~]$ sudo grep -r redis /var/lib/config-data/puppet-generated/* | egrep -v -e ":#"
/var/lib/config-data/puppet-generated/haproxy/etc/haproxy/haproxy.cfg:listen redis
/var/lib/config-data/puppet-generated/redis/etc/security/limits.d/redis.conf:redis soft nofile 10240
/var/lib/config-data/puppet-generated/redis/etc/security/limits.d/redis.conf:redis hard nofile 10240
/var/lib/config-data/puppet-generated/redis/etc/redis.conf:pidfile /var/run/redis/redis.pid
/var/lib/config-data/puppet-generated/redis/etc/redis.conf:unixsocket /var/run/redis/redis.sock
/var/lib/config-data/puppet-generated/redis/etc/redis.conf:logfile /var/log/redis/redis.log
/var/lib/config-data/puppet-generated/redis/etc/redis.conf:dir /var/lib/redis
/var/lib/config-data/puppet-generated/redis/etc/redis.conf.puppet:pidfile /var/run/redis/redis.pid
/var/lib/config-data/puppet-generated/redis/etc/redis.conf.puppet:unixsocket /var/run/redis/redis.sock
/var/lib/config-data/puppet-generated/redis/etc/redis.conf.puppet:logfile /var/log/redis/redis.log
/var/lib/config-data/puppet-generated/redis/etc/redis.conf.puppet:dir /var/lib/redis
~~~
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Deploy overcloud with the default templates
2. Check whether redis, redis vip and telemetry services are enabled
Actual results:
Redis and its vip is enabled while telemtry services are disabled
Expected results:
Redis, its vip and temeletry services are all disabled
Additional info:
I updated bug title because it sounds like an another issue to disable redis vip when redis is disabled.
I think it's better to deal with redis itself in this bug, and address vip in another bz.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2023:4577
Comment 32Red Hat Bugzilla
2023-12-15 04:25:11 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days