我使用vagrant 1.8.1和virtualbox 4.3.28在Ubuntu 14.04上运行我的本地kubernetes v1.1.4集群。一切正常,但自上周五22.01.2016我执行时仍然遇到同样的错误./cluster/kube-up.sh
==> master: * INFO: sh -- Version 2015.11.09
==> master: * INFO: System Information:
==> master: * INFO: CPU: GenuineIntel
==> master: * INFO: CPU Arch: x86_64
==> master: * INFO: OS Name: Linux
==> master: * INFO: OS Version: 3.17.4-301.fc21.x86_64
==> master: * INFO: Distribution: Fedora 21
==> master: * INFO: Installing master
==> master: * INFO: Found function install_fedora_deps
==> master: * INFO: Found function install_fedora_stable
==> master: * INFO: Found function install_fedora_stable_post
==> master: * INFO: Found function install_fedora_restart_daemons
==> master: * INFO: Found function daemons_running
==> master: * INFO: Found function install_fedora_check_services
==> master: * INFO: Running install_fedora_deps()
==> master: which: no dnf in (/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
==> master: * INFO: Adding SaltStack's COPR repository
==> master:
==> master:
==> master: File contains no section headers.
==> master: file: file:///etc/yum.repos.d/saltstack-salt-fedora-21.repo, line: 1
==> master: '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">\n'
==> master: * ERROR: Failed to run install_fedora_deps()!!!
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
我ssh into master,这是/etc/yum.repos.d/saltstack-salt-fedora-21.repo的内容
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="https://copr.fedorainfracloud.org/coprs/saltstack/salt/repo/fedora-21/saltstack-salt-fedora-21.repo">here</a>.</p>
<hr>
<address>Apache/2.4.6 (Red Hat Enterprise Linux) Server at copr.fedoraproject.org Port 80</address>
</body></html>
运行最新的v1.2.0-alpha.6时出现同样的错误。这是salt-fedora21回购的问题吗?任何人都可以复制错误吗?
编辑:相关问题可在https://github.com/kubernetes/kubernetes/issues/20088
找到答案 0 :(得分:5)
这是一个临时修复:
正如https://github.com/kubernetes/kubernetes/issues/20088#issuecomment-174930620中所指出的,根本问题是salt-bootstrap
对基础依赖项引用的URL进行了更改。
这已在https://github.com/saltstack/salt-bootstrap/pull/738中修复,但修复程序尚未使salt-bootstrap
稳定。
我们可以使用develop
版本:
cd cluster/vagrant
sed -i "s/https:\/\/bootstrap.saltstack.com/https:\/\/bootstrap.saltstack.com\/develop/" provision-minion.sh
sed -i "s/https:\/\/bootstrap.saltstack.com/https:\/\/bootstrap.saltstack.com\/develop/" provision-master.sh
在Kubernetes 1.1.4
上进行测试。
答案 1 :(得分:2)
对于那些带有borky bsd sed的macos:
cd cluster/vagrant
sed -e "s/https:\/\/bootstrap.saltstack.com/https:\/\/bootstrap.saltstack.com\/develop/" provision-minion.sh > provision-minion.sh.back
mv provision-minion.sh.back provision-minion.sh
sed -e "s/https:\/\/bootstrap.saltstack.com/https:\/\/bootstrap.saltstack.com\/develop/" provision-master.sh > provision-master.sh.back
mv provision-master.sh.back provision-master.sh