Bug 2154937

Summary:	/openstack/healthcheck missing from designate container images
Product:	Red Hat OpenStack	Reporter:	François Rigault <frigo>
Component:	openstack-tripleo-heat-templates	Assignee:	OSP Team <rhos-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	17.0 (Wallaby)	CC:	amoralej, beagles, bshephar, gthiemon, mariel, mburns, njohnston, oschwart, rhos-maint
Target Milestone:	ga	Keywords:	Reopened, 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-31 15:33:58 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 François Rigault 2022-12-19 17:09:42 UTC

Description of problem:
designate healthcheck services call /openstack/healthcheck that does not exist

Version-Release number of selected component (if applicable):
RHOSP16.2.4
registry.redhat.io/rhosp-rhel8/openstack-designate-central:16.2.4-10
openstack-tripleo-heat-templates-11.6.1-2.20221010235135.el8ost.noarch

How reproducible:
deploy a RHOSP 16.x platform with designate

Steps to Reproduce:
1. deploy overcloud
2. go on a controller
3. systemctl list-units --failed

Actual results:
  UNIT                                           LOAD   ACTIVE SUB    DESCRIPTION                           
● tripleo_designate_central_healthcheck.service  loaded failed failed tripleo_designate_central healthcheck 
● tripleo_designate_mdns_healthcheck.service     loaded failed failed tripleo_designate_mdns healthcheck    
● tripleo_designate_producer_healthcheck.service loaded failed failed tripleo_designate_producer healthcheck
● tripleo_designate_worker_healthcheck.service   loaded failed failed tripleo_designate_worker healthcheck  

Expected results:
no failed service

Additional info:
this is empty:
podman run -ti --rm registry.redhat.io/rhosp-rhel8/openstack-designate-central:16.2.4-10 ls /openstack/

unlike:
podman run -ti --rm registry.redhat.io/rhosp-rhel8/openstack-glance-api:16.2.4 ls /openstack/healthcheck
/openstack/healthcheck

the healthcheck is called from
https://github.com/openstack/tripleo-heat-templates/blob/stable/train/deployment/experimental/designate/designate-central-container-puppet.yaml#L173

Comment 1 Gregory Thiemonge 2023-01-03 15:55:00 UTC

Closed as WONTFIX, Designate is not supported in RHOSP 16.2

The support for Designate was added in RHOSP 17.0

Comment 2 François Rigault 2023-01-04 08:20:25 UTC

exact same issue with 17.0, although the service name is ugly

[stack@all-in-one ~]$ rpm -q openstack-tripleo-heat-templates
openstack-tripleo-heat-templates-14.3.1-0.20220719171727.feca772.el9ost.noarch

[stack@all-in-one ~]$ systemctl list-units --failed
  UNIT                                                                     LOAD   ACTIVE SUB    DESCRIPTION                                                                                     
● 2ebea5068da25f4720e82dc2513b56dba29b68321d9b82ece6d5474f2e257ef0.service loaded failed failed /usr/bin/podman healthcheck run 2ebea5068da25f4720e82dc2513b56dba29b68321d9b82ece6d5474f2e257ef0
● 6f09760936ff84aacfa080c7f70963e7b53291960b308b9b817f1070e4713fa0.service loaded failed failed /usr/bin/podman healthcheck run 6f09760936ff84aacfa080c7f70963e7b53291960b308b9b817f1070e4713fa0
● cd33bb7203bb91ebf559c86e644596416c18a99a4be71ddb6501b0039469c084.service loaded failed failed /usr/bin/podman healthcheck run cd33bb7203bb91ebf559c86e644596416c18a99a4be71ddb6501b0039469c084
● e767d355157fd423e17b58c72f5e548a875942b59fd773239e1dc6223cc0266b.service loaded failed failed /usr/bin/podman healthcheck run e767d355157fd423e17b58c72f5e548a875942b59fd773239e1dc6223cc0266b
● ee5cd28797a8e38b3c89eee7fb1a1fd302b59b4daa2f2b0097d4652d014c19fe.service loaded failed failed /usr/bin/podman healthcheck run ee5cd28797a8e38b3c89eee7fb1a1fd302b59b4daa2f2b0097d4652d014c19fe

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.


[stack@all-in-one ~]$ sudo podman inspect 2ebea5068da25f4720e82dc2513b56dba29b68321d9b82ece6d5474f2e257ef0 -f "{{ .ImageName }}"
registry/rhosp-rhel9/openstack-designate-producer:17.0

[stack@all-in-one ~]$ sudo podman inspect 2ebea5068da25f4720e82dc2513b56dba29b68321d9b82ece6d5474f2e257ef0 -f "{{ .State.Health }}"
{unhealthy 20 [{2023-01-04T08:17:59.650469045Z 2023-01-04T08:17:59.750696844Z 1 /bin/sh: line 1: /openstack/healthcheck: No such file or directory} {2023-01-04T08:18:30.367726756Z 2023-01-04T08:18:30.470652877Z 1 /bin/sh: line 1: /openstack/healthcheck: No such file or directory} {2023-01-04T08:19:01.492428485Z 2023-01-04T08:19:01.702137197Z 1 /bin/sh: line 1: /openstack/healthcheck: No such file or directory} {2023-01-04T08:19:32.751225486Z 2023-01-04T08:19:33.011042634Z 1 /bin/sh: line 1: /openstack/healthcheck: No such file or directory} {2023-01-04T08:20:03.220930631Z 2023-01-04T08:20:03.625507233Z 1 /bin/sh: line 1: /openstack/healthcheck: No such file or directory}]}

Comment 8 Red Hat Bugzilla 2023-12-02 04:26:14 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days