| Summary: | F5 router cannot running | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | zhaozhanqi <zzhao> |
| Component: | Networking | Assignee: | Troy Dawson <tdawson> |
| Networking sub component: | router | QA Contact: | zhaozhanqi <zzhao> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | aos-bugs, bbennett, bleanhar, bmeng, zzhao |
| Version: | 3.1.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-01-29 20:58:42 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
My env meet some error, I will verify this issue once the env is rollback. sorry for that. I think we should leave this bug ON_QA since is at least ready for QE to test (when your environment is rolled back). verified this bug with openshift3/ose-f5-router:latest image id 2cc63b4efbe1 registry.qe.openshift.com/openshift3/ose-f5-router latest 2cc63b4efbe1 2 days ago 440.3 MB |
@zhaozhanqi / @brenton that looks like a packaging issue. The docker image should contain a symlink that points the /usr/bin/openshift binary -- here's the relevant lines from the Dockerfile for images/origin ADD bin/openshift /usr/bin/openshift RUN ln -s /usr/bin/openshift /usr/bin/oc && \ ln -s /usr/bin/openshift /usr/bin/oadm && \ ... ln -s /usr/bin/openshift /usr/bin/openshift-f5-router && \ And the dockerfile for the F5 router has just 2 lines: FROM openshift/origin ENTRYPOINT ["/usr/bin/openshift-f5-router"] deriving from the openshift/origin image. You could check the file contents by doing a : docker export $containerId > foo.tar tar -tvf foo.tar