Bug 53043 – Docker Healthcheck not healthy with proxy in network

Bug 53043 - Docker Healthcheck not healthy with proxy in network


Summary:	Docker Healthcheck not healthy with proxy in network

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	App Center
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	App Center maintainers
QA Contact:	App Center maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2021-04-09 09:39 CEST by Dirk Schnick
Modified:	2021-04-09 11:02 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.023
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2021031921000489
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dirk Schnick

2021-04-09 09:39:19 CEST

A customer noticed, that the health check of the gitlab app fails in their environment. The healthcheck calls https://0.0.0.0:8181/gitlab/help what will be directed to the proxy. From my understanding it should be checked if http://<hostname -f>/gitlab/help is reachable. Alternatively other checks than the network could be tested instead.
The workaround setting the hostname was working at the customer environment. I'm not sure if it is possible to customize the healthcheck during app installation, but if it is, we should do.

I primary opened that bug as we focus more dockerization and proxies in the environment could cause some problems like that. The usage of 0.0.0.0 is from my understanding no good idea, if proxies are in use.

The attached ticked shows more details.