Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

HAProxy unable to start on OpenShift with the default ``cr.yaml`` file

Description

Using default cr.yaml results in a non-functional haproxy instance on OpenShift 4.5.7.  HAproxy fails with error:

Workaround

Use the image from perconalab, replace line 96 in cr.yaml file:

Steps to Reproduce

 

Environment

None

AFFECTED CS IDs

277415, CS0012146

Smart Checklist

Activity

Michael Coburn September 2, 2020 at 2:30 PM

adding ZD 

Slava Sarzhan September 2, 2020 at 2:05 PM

 Yes we had this issue for openshift but it was fixed that is why you can fix it using the latest image  from perconalab. The fix will be available in the next release.

Michael Coburn September 2, 2020 at 2:02 PM

I spoke with  and when is merged it should fix this error.

Done

Details

Assignee

Reporter

Time tracking

20m logged

Fix versions

Affects versions

Priority

Smart Checklist

Created September 2, 2020 at 2:01 PM
Updated March 5, 2024 at 6:08 PM
Resolved September 9, 2020 at 5:33 AM