应用程序路由在 OpenShift Online 3.9 中停止工作
route to application stopped working in OpenShift Online 3.9
我在 Openshift Online starter 中有一个应用程序 运行，它在过去 5 个月内一直有效。服务后面的单个 pod，其定义的路由执行边缘 tls 终止。
从星期六开始，当我尝试访问该应用程序时，收到错误消息
Application is not available
The application is currently not serving requests at this endpoint. It may not have been started or is still starting.
Possible reasons you are seeing this page:
The host doesn't exist. Make sure the hostname was typed correctly and that a route matching this hostname exists.
The host exists, but doesn't have a matching path. Check if the URL path was typed correctly and that the route was created using the desired path.
Route and path matches, but all pods are down. Make sure that the resources exposed by this route (pods, services, deployment configs, etc) have at least one pod running.
pod 是 运行，我可以执行它并检查它，我可以端口转发到它并访问它。
使用 oc 检查不同的组件：
$ oc get po -o wide
NAME READY STATUS RESTARTS AGE IP NODE
taboo3-23-jt8l8 1/1 Running 0 1h 10.128.37.90 ip-172-31-30-113.ca-central-1.compute.internal
$ oc get svc
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
taboo3 172.30.238.44 <none> 8080/TCP 151d
$ oc describe svc taboo3
Name: taboo3
Namespace: sothawo
Labels: app=taboo3
Annotations: openshift.io/generated-by=OpenShiftWebConsole
Selector: deploymentconfig=taboo3
Type: ClusterIP
IP: 172.30.238.44
Port: 8080-tcp 8080/TCP
Endpoints: 10.128.37.90:8080
Session Affinity: None
Events: <none>
$ oc get route
NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD
taboo3 taboo3-sothawo.193b.starter-ca-central-1.openshiftapps.com taboo3 8080-tcp edge/Redirect None
我也尝试添加一条新路由（有或没有 tls），但我遇到了同样的错误。
是否有人知道可能导致此问题的原因以及解决方法？
2018 年 4 月 17 日添加：收到来自 Openshift 在线支持的电子邮件：
It looks like you may be affected by this bug.
所以等待解决。
问题已通过 Openshift Online 解决，应用程序恢复正常
我在 Openshift Online starter 中有一个应用程序 运行，它在过去 5 个月内一直有效。服务后面的单个 pod，其定义的路由执行边缘 tls 终止。
从星期六开始，当我尝试访问该应用程序时，收到错误消息
Application is not available The application is currently not serving requests at this endpoint. It may not have been started or is still starting.
Possible reasons you are seeing this page:
The host doesn't exist. Make sure the hostname was typed correctly and that a route matching this hostname exists.
The host exists, but doesn't have a matching path. Check if the URL path was typed correctly and that the route was created using the desired path.
Route and path matches, but all pods are down. Make sure that the resources exposed by this route (pods, services, deployment configs, etc) have at least one pod running.
pod 是 运行，我可以执行它并检查它，我可以端口转发到它并访问它。
使用 oc 检查不同的组件：
$ oc get po -o wide
NAME READY STATUS RESTARTS AGE IP NODE
taboo3-23-jt8l8 1/1 Running 0 1h 10.128.37.90 ip-172-31-30-113.ca-central-1.compute.internal
$ oc get svc
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
taboo3 172.30.238.44 <none> 8080/TCP 151d
$ oc describe svc taboo3
Name: taboo3
Namespace: sothawo
Labels: app=taboo3
Annotations: openshift.io/generated-by=OpenShiftWebConsole
Selector: deploymentconfig=taboo3
Type: ClusterIP
IP: 172.30.238.44
Port: 8080-tcp 8080/TCP
Endpoints: 10.128.37.90:8080
Session Affinity: None
Events: <none>
$ oc get route
NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD
taboo3 taboo3-sothawo.193b.starter-ca-central-1.openshiftapps.com taboo3 8080-tcp edge/Redirect None
我也尝试添加一条新路由（有或没有 tls），但我遇到了同样的错误。
是否有人知道可能导致此问题的原因以及解决方法？
2018 年 4 月 17 日添加：收到来自 Openshift 在线支持的电子邮件：
It looks like you may be affected by this bug.
所以等待解决。
问题已通过 Openshift Online 解决，应用程序恢复正常