https health checks by ldirectord fail

Bug #1394759 reported by Shawn Heisey
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
resource-agents (Ubuntu)
Fix Released
Undecided
Unassigned
Precise
Won't Fix
Undecided
Unassigned
Trusty
Won't Fix
Undecided
Unassigned
Bionic
Fix Released
Undecided
Unassigned

Bug Description

Package: ldirectord
Description: Ubuntu 14.04.1 LTS
Release: 14.04

See debian bug 770349. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770349

For https health checks to succeed, the verify_hostname option for LWP must be disabled. If an IP address is used for the real server (which as far as I know is recommended), the hostname in the request will not match the name in the SSL certificate. Newer LWP versions will check that these match unless they are told not to.

The upstream fix was committed here:

https://github.com/mcnewton/resource-agents/commit/68fad38326b7c04efd6434e736e32fe395eafe02

I am awaiting another maintenance window before I can verify that this patch fixes the problem I encountered.

Revision history for this message
Shawn Heisey (elyograg) wrote :

I have verified in a lab environment that the patch fixes the I encountered when trying to replace a CentOS 5 load balancer with one running Ubuntu 14.

Revision history for this message
Rafael David Tinoco (rafaeldtinoco) wrote :

Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.

$ git describe 68fad38326b7c04efd6434e736e32fe395eafe02
v3.9.5-228-g68fad383

resource-agents | 1:3.9.2-5ubuntu4 | precise |
resource-agents | 1:3.9.2-5ubuntu4.1 | precise-updates |
resource-agents | 1:3.9.3+git20121009-3ubuntu2 | trusty |
resource-agents | 1:3.9.7-1 | xenial |
resource-agents | 1:3.9.7-1ubuntu1.1 | xenial-updates |
resource-agents | 1:4.1.0~rc1-1ubuntu1 | bionic |
resource-agents | 1:4.1.0~rc1-1ubuntu1.2 | bionic-updates |
resource-agents | 1:4.2.0-1ubuntu1 | disco |
resource-agents | 1:4.2.0-1ubuntu1.1 | disco-updates |
resource-agents | 1:4.2.0-1ubuntu2 | eoan |
resource-agents | 1:4.4.0-3ubuntu1 | focal |

I'm marking Precise and Trusty as won't fix due to release schedule
and marking all others as Fix Released according to your bug desc.

It is unfortunate that we were unable to resolve this defect, however
there appears to be no further action possible at this time. I am
therefore moving the bug to 'won't fix'. If you disagree or have
new information, we would be grateful if you could please add a comment
stating why and then change the status of the bug to 'New'.

Changed in resource-agents (Ubuntu Precise):
status: New → Won't Fix
Changed in resource-agents (Ubuntu Trusty):
status: New → Won't Fix
Changed in resource-agents (Ubuntu Bionic):
status: New → Fix Released
Changed in resource-agents (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.