我成功安装了openshift 3.9,但WebConsole无法正常工作,我猜不存在。
版oc v3.9.0+ba7faec-1
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server: ***
openshift v3.9.0+ba7faec-1
kubernetes v1.9.1+a0ce1bc657
项目网络控制台不存在,网页错误是:
missing service (service "webconsole" not found)
missing route (service "webconsole" not found)
重现步骤
INSTALLER STATUS *********************************************************************************************************************************************************************************
Initialization : Complete (0:00:31)
Web Console Install : Complete (0:00:04)
此安装过程并没有产生效果,
接下来我尝试从此指令安装Web控制台: https://github.com/openshift/origin-web-console-server#installing-the-console
但是,这个带有webconsole的pod一直处于待定状态......
有错误:
Warning FailedScheduling 4s (x8 over 1m) default-scheduler 0/1 nodes are available: 1 MatchNodeSelector.
任何想法?
编辑:
oc -n openshift-web-console describe pod
Name: webconsole-675b8c8779-h65gl
Namespace: openshift-web-console
Node: <none>
Labels: app=openshift-web-console
pod-template-hash=2316474335
webconsole=true
Annotations: openshift.io/scc=restricted
Status: Pending
IP:
Controlled By: ReplicaSet/webconsole-675b8c8779
Containers:
webconsole:
Image: openshift/origin-web-console:v3.9.0
Port: 8443/TCP
Command:
/usr/bin/origin-web-console
--audit-log-path=-
-v=0
--config=/var/webconsole-config/webconsole-config.yaml
Requests:
cpu: 100m
memory: 100Mi
Liveness: exec [/bin/sh -c if [[ ! -f /tmp/webconsole-config.hash ]]; then
\
md5sum /var/webconsole-config/webconsole-config.yaml > /tmp/webconsole-
config.hash; \
elif [[ $(md5sum /var/webconsole-config/webconsole-config.yaml) != $(cat
/tmp/webconsole-config.hash) ]]; then \
echo 'webconsole-config.yaml has changed.'; \
exit 1; \
fi && curl -k -f https://0.0.0.0:8443/console/] delay=0s timeout=1s
period=10s #success=1 #failure=3
Readiness: http-get https://:8443/healthz delay=0s timeout=1s period=10s
#success=1 #failure=3
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from webconsole-token-xgmj2
(ro)
/var/serving-cert from serving-cert (rw)
/var/webconsole-config from webconsole-config (rw)
Conditions:
Type Status
PodScheduled False
Volumes:
serving-cert:
Type: Secret (a volume populated by a Secret)
SecretName: webconsole-serving-cert
Optional: false
webconsole-config:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: webconsole-config
Optional: false
webconsole-token-xgmj2:
Type: Secret (a volume populated by a Secret)
SecretName: webconsole-token-xgmj2
Optional: false
QoS Class: Burstable
Node-Selectors: node-role.kubernetes.io/compute=true
Tolerations: node.kubernetes.io/memory-pressure:NoSchedule
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 1m (x37 over 11m) default-scheduler 0/1 nodes
are available: 1 MatchNodeSelector.
oc -n openshift-web-console get event
LAST SEEN FIRST SEEN COUNT NAME
KIND SUBOBJECT TYPE REASON SOURCE
MESSAGE
4m 20m 57 webconsole-675b8c8779-
h65gl.1528f23510e2d8d3 Pod Warning FailedScheduling
default-scheduler 0/1 nodes are available: 1 MatchN
.
20m 20m 2 webconsole-675b8c8779.1528f234d40fd602
ReplicaSet Warning FailedCreate replicaset-controller
Error creating: pods "webconsole-
" is forbidden: error looking up service account openshift-web-
console/webconsole: serviceaccount "webconsole" not found
20m 20m 1 webconsole-675b8c8779.1528f23510db69ee
ReplicaSet Normal SuccessfulCreate replicaset-controller
Created pod: webconsole-675b8c877
20m 20m 1 webconsole.1528f234d3694bcc
Deployment Normal ScalingReplicaSet deployment-controller
Scaled up replica set webconsole-
to 1
答案 0 :(得分:0)
根据您的错误消息,您可能会点击issue#6930。验证您的库存配置是否将主节点设置为openshift_schedulable=true
。您可以使用oc describe node <node>
验证这一点。您可以参考documentation了解如何更改此安装后的内容。
但是,当无法访问控制台时,您的安装成功很奇怪。