Bug 1355880 - router fails to start in 3.2.1.6 - haproxy-config.template:223: function "matchValues" not defined
Summary: router fails to start in 3.2.1.6 - haproxy-config.template:223: function "mat...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.2.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Jason DeTiberus
QA Contact: Mike Fiedler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-12 19:34 UTC by Mike Fiedler
Modified: 2016-09-06 19:50 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-06 19:50:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Mike Fiedler 2016-07-12 19:34:38 UTC 
Description of problem:

Installed 3.2.1.6 and tried to create an haproxy router.   It immediately goes into CrashLoopBackoff with this error in the pod log:

error: template: haproxy-config.template:223: function "matchValues" not defined



Version-Release number of selected component (if applicable): 

3.2.1.6


How reproducible: Always


Steps to Reproduce:
1.  Install 3 node cluster on AWS using aws_install_prep and BYO playbooks
2.  After installation, a router pod exists and is in CrashLoopBackoff with the above error.
3.  Tried deleting and re-createing the router with oadm router --config=/etc/origin/master/admin.kubeconfig --replicas=1 and the same thing occurred

Actual results:

Router will not run - error: template: haproxy-config.template:223: function "matchValues" not defined
Comment 1 Scott Dodson 2016-07-17 19:58:23 UTC 
This was an image build error, should be fixed in v3.2.1.9. If it is, lets move this to closed notabug?
Comment 2 Mike Fiedler 2016-07-18 16:32:00 UTC 
Verified on 3.2.1.9
Note You need to log in before you can comment on or make changes to this bug.