Bug 2025451

Summary: [RFE] [RHOSP 16.1] redis resource is not disabled by default even though other legacy telemetry components are by default disabled
Product: Red Hat OpenStack Reporter: Punit Kundal <pkundal>
Component: rhosp-directorAssignee: OSP Team <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: David Rosenfeld <drosenfe>
Severity: low Docs Contact:
Priority: low    
Version: 16.1 (Train)CC: lmiccini, mburns, morazi, pgrist, shtiwari, tkajinam
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-24 05:18:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Punit Kundal 2021-11-22 09:10:41 UTC
Description of problem:

there are legacy telemetry ceilometer, aodh and gnocchi which is disabled by default in RHOSP 16.1

even though these are disabled; we still have redis resource in pacemaker which is enabled and redis resource is only used by gnocchi as a temporary store for metric for aggregation

+++
[root@overcloud-controller-0 ~]# podman ps | grep -e aodh -e gnocchi
[root@overcloud-controller-0 ~]# pcs status
Cluster name: tripleo_cluster
Cluster Summary:
  * Stack: corosync
  * Current DC: overcloud-controller-0 (version 2.0.3-5.el8_2.3-4b1f869f0f) - partition with quorum
  * Last updated: Mon Nov 22 09:08:18 2021
  * Last change:  Mon Nov 22 09:05:38 2021 by hacluster via crmd on overcloud-controller-0
  * 4 nodes configured
  * 13 resource instances configured

Node List:
  * Online: [ overcloud-controller-0 ]
  * GuestOnline: [ galera-bundle-0@overcloud-controller-0 rabbitmq-bundle-0@overcloud-controller-0 redis-bundle-0@overcloud-controller-0 ]

Full List of Resources:
  * Container bundle: galera-bundle [cluster.common.tag/openstack-mariadb:pcmklatest]:
    * galera-bundle-0	(ocf::heartbeat:galera):	Master overcloud-controller-0
  * Container bundle: rabbitmq-bundle [cluster.common.tag/openstack-rabbitmq:pcmklatest]:
    * rabbitmq-bundle-0	(ocf::heartbeat:rabbitmq-cluster):	Started overcloud-controller-0
  * Container bundle: redis-bundle [cluster.common.tag/openstack-redis:pcmklatest]:
    * redis-bundle-0	(ocf::heartbeat:redis):	Master overcloud-controller-0
  * ip-192.168.24.20	(ocf::heartbeat:IPaddr2):	Started overcloud-controller-0
  * ip-192.168.24.10	(ocf::heartbeat:IPaddr2):	Started overcloud-controller-0
  * Container bundle: haproxy-bundle [cluster.common.tag/openstack-haproxy:pcmklatest]:
    * haproxy-bundle-podman-0	(ocf::heartbeat:podman):	Started overcloud-controller-0
  * Container bundle: openstack-cinder-volume [cluster.common.tag/openstack-cinder-volume:pcmklatest]:
    * openstack-cinder-volume-podman-0	(ocf::heartbeat:podman):	Started overcloud-controller-0

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled
[root@overcloud-controller-0 ~]# 
+++

Version-Release number of selected component (if applicable):
(undercloud) [stack@undercloud16 ~]$ sudo rpm -qa | grep -e puppet-tripleo -e puppet-pacemaker
puppet-pacemaker-1.0.1-1.20201114034949.el8ost.noarch
puppet-tripleo-11.5.0-1.20201114030109.el8ost.noarch
(undercloud) [stack@undercloud16 ~]$ 


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
redis resource is enabled

Expected results:
redis resource should be disabled by default if one hasn't enabled legacy telemetry

Additional info:

Comment 2 Shravan Kumar Tiwari 2021-11-22 10:27:59 UTC
Customer also wanted to know if this is not disabled by default then running it with the disable-telemetry.yaml should do the job and can it be taken care in that flow?

Comment 3 Takashi Kajinami 2021-11-22 15:24:12 UTC
I think this is duplicate of bz 1823250 ?

Comment 4 Luca Miccini 2021-11-22 15:26:45 UTC
(In reply to Shravan Kumar Tiwari from comment #2)
> Customer also wanted to know if this is not disabled by default then running
> it with the disable-telemetry.yaml should do the job and can it be taken
> care in that flow?

as a rule of thumb setting a service to noop will not actively remove anything, it will leave orphaned resources behind and requires the operator to delete them manually.
We are already working on the redis topic - see the bz that Takashi just linked and the upstream bug https://bugs.launchpad.net/bugs/1872645.

Comment 8 Luca Miccini 2023-07-24 05:18:52 UTC

*** This bug has been marked as a duplicate of bug 1823250 ***