eparis / kubernetes-ansible

Ansible playbooks to build a kubernetes cluster from scratch
336 stars 135 forks source link

f20-public-official image based on openstack, can't run script #4

Closed xiaods closed 9 years ago

xiaods commented 10 years ago
$ ansible-playbook -i inventory hack-network.yml

PLAY [minions] ****************************************************************

GATHERING FACTS ***************************************************************
ok: [10.3.10.61]
ok: [10.3.10.63]
ok: [10.3.10.62]

TASK: [network-hack-bridge | install NetworkManager] **************************
ok: [10.3.10.62]
ok: [10.3.10.63]
ok: [10.3.10.61]

TASK: [network-hack-bridge | Create kubernetes bridge interface] **************
failed: [10.3.10.61] => {"changed": true, "cmd": ["nmcli", "connection", "add", "type", "bridge", "ifname", "kbr0", "con-name", "kubernetes-bridge", "ip4", "10.0.1.1/24"], "delta": "0:00:00.019478", "end": "2014-10-04 05:02:04.718215", "rc": 9, "start": "2014-10-04 05:02:04.698737"}
stderr: Error: nmcli (0.9.9.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.
failed: [10.3.10.62] => {"changed": true, "cmd": ["nmcli", "connection", "add", "type", "bridge", "ifname", "kbr0", "con-name", "kubernetes-bridge", "ip4", "10.0.2.1/24"], "delta": "0:00:00.019926", "end": "2014-10-04 05:02:05.026861", "rc": 9, "start": "2014-10-04 05:02:05.006935"}
stderr: Error: nmcli (0.9.9.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.
failed: [10.3.10.63] => {"changed": true, "cmd": ["nmcli", "connection", "add", "type", "bridge", "ifname", "kbr0", "con-name", "kubernetes-bridge", "ip4", "10.0.3.1/24"], "delta": "0:00:00.026086", "end": "2014-10-04 05:02:05.377111", "rc": 9, "start": "2014-10-04 05:02:05.351025"}
stderr: Error: nmcli (0.9.9.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************************************************************
           to retry, use: --limit @/Users/dxiao/hack-network.retry

10.3.10.61                 : ok=2    changed=0    unreachable=0    failed=1
10.3.10.62                 : ok=2    changed=0    unreachable=0    failed=1
10.3.10.63                 : ok=2    changed=0    unreachable=0    failed=1

dxiao at localhost in ~/Documents/code/test/kubernetes-ansible on master*
$ ssh fedora@10.3.10.61
Last login: Sat Oct  4 05:02:04 2014 from vpn1-113-16.nay.redhat.com
[fedora@dxiao-fedora-kubernetes-3b5087ac-778c-4b18-9472-37ef90905252 ~]$ yum install NetworkManager
You need to be root to perform this command.
[fedora@dxiao-fedora-kubernetes-3b5087ac-778c-4b18-9472-37ef90905252 ~]$ sudo yum install NetworkManager
Package 1:NetworkManager-0.9.9.0-45.git20131003.fc20.x86_64 already installed and latest version
Nothing to do
HackToday commented 9 years ago

Hit similar issues. Did maintainer have any feedback ?

eparis commented 9 years ago

wild wild guess? You updated the NM package, but NetworkManager hasn't restarted. So nmcli is a new version and the copy of the NM daemon running is an old version, and so nmcli refuses to talk to the daemon.

But it's a wild guess. This sure looks like a generic NM issue, not really an ansible issue...

eparis commented 9 years ago

we do networking completely differently now, so this is relevant.