错误：等待条件超时

问题描述 投票：0回答：3

在带有 Docker 18 和 OpenShift OKD oc v3.11.0 的 Ubuntu 18.04 上，本地集群将无法成功启动并产生超时错误消息。

是否可以使用

oc cluster up
在Ubuntu 18.04上启动本地集群？支持吗？ Ubuntu 18.04 上应该如何启动集群。

myuser:~] $ oc cluster up --public-hostname='ocp.127.0.0.1.nip.io' --routing-suffix='apps.ocp.127.0.0.1.nip.io'
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Pulling image openshift/origin-control-plane:v3.11
Pulled 1/5 layers, 23% complete
Pulled 2/5 layers, 43% complete
Pulled 3/5 layers, 80% complete
Pulled 4/5 layers, 96% complete
Pulled 5/5 layers, 100% complete
Extracting
Image pull complete
Pulling image openshift/origin-cli:v3.11
Image pull complete
Pulling image openshift/origin-node:v3.11
Pulled 5/6 layers, 88% complete
Pulled 6/6 layers, 100% complete
Extracting
Image pull complete
Creating shared mount directory on the remote host ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if insecured registry is configured properly in Docker ...
Checking if required ports are available ...
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Starting OpenShift using openshift/origin-control-plane:v3.11 ...
I0416 08:32:35.747717   22853 config.go:40] Running "create-master-config"
I0416 08:32:37.456151   22853 config.go:46] Running "create-node-config"
I0416 08:32:38.721454   22853 flags.go:30] Running "create-kubelet-flags"
I0416 08:32:39.763094   22853 run_kubelet.go:49] Running "start-kubelet"
I0416 08:32:39.972403   22853 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
I0416 08:33:13.978672   22853 interface.go:26] Installing "kube-proxy" ...
I0416 08:33:13.978684   22853 interface.go:26] Installing "kube-dns" ...
I0416 08:33:13.978689   22853 interface.go:26] Installing "openshift-service-cert-signer-operator" ...
I0416 08:33:13.978694   22853 interface.go:26] Installing "openshift-apiserver" ...
I0416 08:33:13.978704   22853 apply_template.go:81] Installing "openshift-apiserver"
I0416 08:33:13.978752   22853 apply_template.go:81] Installing "kube-dns"
I0416 08:33:13.978758   22853 apply_template.go:81] Installing "kube-proxy"
I0416 08:33:13.978788   22853 apply_template.go:81] Installing "openshift-service-cert-signer-operator"
I0416 08:33:15.418545   22853 interface.go:41] Finished installing "kube-proxy" "kube-dns" "openshift-service-cert-signer-operator" "openshift-apiserver"
Error: timed out waiting for the condition



[myuser:~] 1 $ docker version
Client:
 Version:           18.09.1
 API version:       1.39
 Go version:        go1.10.6
 Git commit:        4c52b90
 Built:             Wed Jan  9 19:35:31 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.1
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       4c52b90
  Built:            Wed Jan  9 19:02:44 2019
  OS/Arch:          linux/amd64
  Experimental:     false
[myuser:~] $ oc version
oc v3.11.0+0cbc58b
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
[myuser:~] $ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
[myuser:~] $

我认为这与 Ubuntu 18.04 现在默认使用 dnsmasq 有关。我使用类似于下面的脚本取得了一些成功。

#!/bin/bash
sudo /bin/sh -c 'echo "nameserver 8.8.8.8" > /etc/resolv.conf'
oc cluster up --public-hostname='ocp.127.0.0.1.nip.io' --routing-suffix='apps.ocp.127.0.0.1.nip.io'
oc cluster down
sudo /bin/sh -c 'echo "nameserver 8.8.8.8" > /etc/resolv.conf'
sudo /bin/sh -c 'echo "nameserver 8.8.8.8" > ~/openshift.local.clusterup/kubedns/resolv.conf'
oc cluster up --public-hostname='ocp.127.0.0.1.nip.io' --routing-suffix='apps.ocp.127.0.0.1.nip.io'

所以问题似乎是 

/etc/resolv.conf
在 Ubuntu 18.04 下有所不同，不适合 
oc cluster up
。

尝试上述解决方法后，您可以使用类似于下面的脚本测试 DNS 是否正常工作

#!/bin/bash
oc login -u system:admin -n default
podname=$(oc get pods | grep registry | awk '{print $1;}')
oc exec $podname host github.com
openshift openshift-origin openshift-client-tools
3个回答
0
投票

您可以通过停止计算机上所有正在运行的容器来解决此问题，或者如果您的计算机上还有其他重要的正在运行的容器，请停止 openshift 运行的容器，然后再次运行 oc cluster up 命令：

docker container stop $(docker ps -q)

oc cluster up --skip-registry-check=true
0
投票

在尝试修复所有可能的问题（例如超时、EOF、错误、恐慌和其他随机问题）（我在 oc up 期间遇到了大约 300 次失败）之后，我将虚拟机恢复到安装以下内容之前的状态，并且我已经完成了我猜想是以正确的方式，因为现在它应该像它应该的那样工作（+我可以毫无压力地向上/向下进行 oc 集群）

PS。它还可以限制从 Openshift 提取 Docker 镜像 100 次（尝试 docker run hello-world）。

`sudo apt update && sudo apt upgrade`

`sudo apt install curl`
`curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -`


`sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"`

`sudo apt update && sudo apt -y install docker-ce`

`sudo usermod -aG docker XXXX`

`groups XXXX`


`wget https://github.com/openshift/origin/releases/download/v3.11.0/openshift-origin-client-tools-v3.11.0-0cbc58b-linux-64bit.tar.gz`


`cat << EOF | sudo tee /etc/docker/daemon.json
 {
    "insecure-registries" : [ "172.30.0.0/16" ]
 }
 EOF`

`sudo systemctl daemon-reload`
`sudo systemctl restart docker`

`sudo systemctl is-enabled docker`
`sudo systemctl is-active docker`

问候， 阿图尔

0
投票

删除 openshift 上的构建并重新构建。它对我有用

最新问题
© www.soinside.com 2019 - 2024. All rights reserved.