Bug 1664953
Summary: | router pods can not be started, no /usr/bin/openshift-router | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Yadan Pei <yapei> |
Component: | Networking | Assignee: | Dan Mace <dmace> |
Networking sub component: | router | QA Contact: | Hongan Li <hongli> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | urgent | ||
Priority: | high | CC: | aos-bugs, mifiedle, scheng, xxia, yapei |
Version: | 4.1.0 | Keywords: | TestBlocker |
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:41: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: | |
Embargoed: |
Description
Yadan Pei
2019-01-10 06:50:44 UTC
Marking this TestBlocker since it blocks access to all routes, including the console. How was this cluster created? Tested with latest build and the issue has been fixed. $ oc get clusterversions.config.openshift.io NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-01-11-000044 True False 48m Cluster version is 4.0.0-0.nightly-2019-01-11-000044 $ oc get clusterversion version -o yaml | grep -i payload payload: registry.svc.ci.openshift.org/ocp/release@sha256:4d4b4f0c64c5a27aeaeb43a5c27ba0b0a2b4c13bad7e290d712bdfd5793da7f2 $ oc get pods -n openshift-ingress NAME READY STATUS RESTARTS AGE router-default-bb6dfcb9-779x2 1/1 Running 0 52m $ oc get pods -n openshift-ingress -o yaml | grep image image: registry.svc.ci.openshift.org/ocp/4.0-art-latest-2019-01-11-000044@sha256:9f7426e0e6a8b20d5b4af94f498e832985de36e2f06eadd2d92d652d198446ea $ curl http://service-unsecure-hongli.apps.qe-jialiu3.qe.devcluster.openshift.com Hello-OpenShift-1 http-8080 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758 |