Bug 1386157 - Haproxy router cannot be running due to the Dockerfile is old
Summary: Haproxy router cannot be running due to the Dockerfile is old
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.4.0
Hardware: All
OS: All
high
high
Target Milestone: ---
: ---
Assignee: Troy Dawson
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-18 10:01 UTC by zhaozhanqi
Modified: 2022-08-04 22:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-27 14:29:56 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description zhaozhanqi 2016-10-18 10:01:02 UTC
Description of problem:
haproxy router pod cannot be running due to ' error creating config file /var/lib/haproxy/conf/cert_config.map: open /var/lib/haproxy/conf/cert_config.map: permission denied'

Enter the container found the Dockerfile is old, see 

cat /var/lib/haproxy/Dockerfile
<--snip-->
RUN INSTALL_PKGS="haproxy" && \
    yum install -y $INSTALL_PKGS && \
    rpm -V $INSTALL_PKGS && \
    mkdir -p /var/lib/haproxy/router/{certs,cacerts} && \
    mkdir -p /var/lib/haproxy/{conf,run,bin,log} && \
    touch /var/lib/haproxy/conf/{{os_http_be,os_edge_http_be,os_tcp_be,os_sni_passthrough,os_reencrypt,os_edge_http_expose,os_edge_http_redirect}.map,haproxy.config} && \
    chmod -R 777 /var && \

<--snip>

Version-Release number of selected component (if applicable):
 #openshift version
openshift v3.4.0.12
kubernetes v1.4.0+776c994
etcd 3.1.0-alpha.1


haproxy images(v3.4.0.12  id: 8625fccc7755)

How reproducible:
always

Steps to Reproduce:
1. Create haproxy router using
 oadm router
2. Check the logs
  docker logs 
3.

Actual results:
router always restart 

docker logs:

 1 ratelimiter.go:52] error creating config file /var/lib/haproxy/conf/cert_config.map: open /var/lib/haproxy/conf/cert_config.map: permission denied


Expected results:
router can be running and work well

Additional info:

Comment 3 Troy Dawson 2016-10-21 17:34:05 UTC
This is fixed and should be in v3.4.0.14 or newer images.

Comment 4 zhaozhanqi 2016-10-24 03:34:54 UTC
tested with haproxy router images (id=762f5cbc271c). this issue has been fixed.

Mark this bug to 'verified'

Comment 5 Troy Dawson 2016-10-27 14:29:56 UTC
Marking this Closed current release.  The bug was never released to customers and it is fixed in the current released testing images.


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