我正在运行openshift监视命令，而在运行oc adm diagnostics appcreate时，我会遇到以下错误
[root@amos01-master1-Paris ec2-user]# oc adm diagnostics appcreate
[Note] Determining if client configuration exists for client/cluster diagnostics
Info: Successfully read a client config file at '/root/.kube/config'
Info: Using context for cluster-admin access: 'test2/master01-Paris-amosdemo-io:8443/system:admin'
[Note] Running diagnostic: AppCreate
Description: Create an application and test that it deploys correctly.
I0812 06:38:00.061839 10229 logs.go:41] Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 200 OK\r\n"; err=<nil>
Info: 06:37:50.843: Using project 'openshift-diagnostic-appcreate-66t72' for diagnostic.
Info: 06:37:58.806: App 'diagnostic-appcreate' is running
Info: 06:37:59.563: Request to service address http://172.30.6.2:8080/ succeeded
ERROR: [DCluAC030 from diagnostic AppCreate@openshift/origin/pkg/oc/admin/diagnostics/diagnostics/cluster/app_create/route.go:140]
06:38:04.602: Request to route http://diagnostic-appcreate-openshift-diagnostic-appcreate-66t72.apps01-Paris.amosdemo.io:80/ with timeout 500ms failed after 11 tries.
Last error was: Get http://diagnostic-appcreate-openshift-diagnostic-appcreate-66t72.apps01-Paris.amosdemo.io:80/: dial tcp: lookup diagnostic-appcreate-openshift-diagnostic-appcreate-66t72.apps01-Paris.amosdemo.io on 172.32.96.253:53: no such host
Diagnostics attempted to connect to the admitted route for the test application,
expecting to receive a successful response with HTTP code 200. This did not happen
within the given timeout.
Some of the reasons why this may fail include:
* The host running this diagnostic is not configured to resolve the route host via DNS
(try running from a different host, or skip the route connection test)
* The router has not yet started routing the route's host after admitting it
(try increasing the diagnostic timeout or number of retries)
* The pod stopped or was killed after starting successfully (check pod/node logs)
* The pod is responding with a non-200 HTTP code (or, not quickly enough / at all)
* Cluster networking problems prevent the router from connecting to the service
Info: App creation and readiness completed with success=true in 7.853013947s
Info: Service creation and testing completed with success=true in 757.44834ms
Info: Route creation and testing completed with success=false in 5.038546344s
Info: Entire create/test completed with success=false in 13.758380242s
[Note] Summary of diagnostics execution (version v3.9.89):
[Note] Errors seen: 1
该项目未创建，或者根本没有人可以弄清楚问题所在吗？