contiv-experimental/demo

Docker public key problem during istallation

smolit opened this issue · 1 comments

Hi @ALL,

while running net_demo_installer script I am getting an error @task [docker | add docker's public key for CS-engine (debian)](see end of output).
Is there a solution availabel?

Thank you in advance
Sebastian

labor@ubuntu15-1:~$ ./net_demo_installer
Using version: v0.1-07-14-2016.07-06-17.UTC

W: Fehlschlag beim Holen von http://ppa.launchpad.net/ansible/ansible/ubuntu/dists/wily/main/binary-i386/Packages 403 Forbidden

E: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt.

  • sudoExec apt-get install wget git build-essential python-dev software-properties-common -y

  • sudo -E apt-get install wget git build-essential python-dev software-properties-common -y
    Paketlisten werden gelesen... Fertig
    Abhängigkeitsbaum wird aufgebaut.
    Statusinformationen werden eingelesen.... Fertig
    build-essential ist schon die neueste Version.
    python-dev ist schon die neueste Version.
    git ist schon die neueste Version.
    software-properties-common ist schon die neueste Version.
    wget ist schon die neueste Version.
    0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

  • sudoExec apt-add-repository -y ppa:ansible/ansible

  • sudo -E apt-add-repository -y ppa:ansible/ansible
    gpg: Schlüsselbund /tmp/tmpjrlt0wyy/secring.gpg' erstellt gpg: Schlüsselbund/tmp/tmpjrlt0wyy/pubring.gpg' erstellt
    gpg: Schlüssel 7BB9C367 von hkp-Server keyserver.ubuntu.com anfordern
    gpg: /tmp/tmpjrlt0wyy/trustdb.gpg: trust-db erzeugt
    gpg: Schlüssel 7BB9C367: Öffentlicher Schlüssel "Launchpad PPA for Ansible, Inc." importiert
    gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
    gpg: importiert: 1 (RSA: 1)
    OK

  • sudoExec apt-get install -y ansible

  • sudo -E apt-get install -y ansible
    Paketlisten werden gelesen... Fertig
    Abhängigkeitsbaum wird aufgebaut.
    Statusinformationen werden eingelesen.... Fertig
    ansible ist schon die neueste Version.
    0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

  • [[ Ubuntu =~ ^CentOS ]]
    ++ which ansible

  • '[' /usr/bin/ansible == '' ']'

  • set +x
    Parsing config file...

         ==== Contiv Netplugin Demo Installer ====
    

Netplugin Cluster will be set up on the following servers in Standalone mode:

10.10.0.164

Ready to proceed(y/n)? y

  • '[' -d ansible ']'
  • cd ansible
  • git pull --rebase origin
    Aktueller Branch master ist auf dem neuesten Stand.
  • cd ..
  • '[' latest '!=' latest ']'
  • set +xe
    Verifying ansible reachability
    Verifying OS versions on all hosts...
    ++ sed 's/[",]//g'
    ++ awk -F: '/(<ansible_distribution>|<ansible_distribution_version>)/{print $2}' .gen/hosts.log
  • items=' Ubuntu
    15.10'
  • i=0
  • os=
  • ver=
  • for item in '${items[@]}'
  • '[' 0 == 0 ']'
  • os=Ubuntu
  • i=1
  • for item in '${items[@]}'
  • '[' 1 == 0 ']'
  • ver=15.10
  • CheckOSTypeAndVersion Ubuntu 15.10
  • os=Ubuntu
  • CheckOSType Ubuntu
  • [[ ! Ubuntu =~ ^(Ubuntu|CentOS) ]]
  • echo OS is supported.
    OS is supported.
  • return 0
  • ver=15.10
  • [[ Ubuntu =~ ^Ubuntu ]]
  • CheckOSVersion 15.10 '15.*'
  • [[ ! 15.10 =~ ^15.* ]]
  • echo OS version matched.
    OS version matched.
  • return 0
  • [[ Ubuntu =~ ^CentOS ]]
  • i=0
  • set +x
    Verifying sudo access on all hosts...

Ansible access and OS version verification completed on all hosts

Contents of ./.gen/contiv_hosts:

[netplugin-node]

node1 ansible_ssh_host=10.10.0.164 contiv_network_mode=standalone control_interface=eth0 netplugin_if=eth1 fwd_mode=bridge

Setting up services on nodes

PLAY [devtest] ****************************************************************
skipping: no hosts matched

PLAY [volplugin-test] *********************************************************
skipping: no hosts matched

PLAY [cluster-node] ***********************************************************
skipping: no hosts matched

PLAY [cluster-control] ********************************************************
skipping: no hosts matched

PLAY [service-master] *********************************************************
skipping: no hosts matched

PLAY [service-worker] *********************************************************
skipping: no hosts matched

PLAY [netplugin-node] *********************************************************

GATHERING FACTS ***************************************************************
ok: [node1]

TASK: [base | upgrade system (debian)] ****************************************
ok: [node1]

TASK: [base | install base packages (debian)] *********************************
ok: [node1] => (item=ntp,unzip,bzip2,curl,python-software-properties,bash-completion,python-selinux,e2fsprogs,openssh-server)

TASK: [base | install epel release package (redhat)] **************************
skipping: [node1]

TASK: [base | install/upgrade base packages (redhat)] *************************
skipping: [node1]

TASK: [base | install and start ntp] ******************************************
skipping: [node1]

TASK: [docker | check docker version] *****************************************
changed: [node1]

TASK: [docker | create docker daemon's config directory] **********************
ok: [node1]

TASK: [docker | setup docker daemon's environment] ****************************
ok: [node1]

TASK: [docker | add docker's public key for CS-engine (debian)] ***************
failed: [node1] => {"failed": true}
msg: Failed to download key at https://sks-keyservers.net/pks/lookup?op=get&search=0xee6d536cf7dc86e2d7d56f59a178ac6c6238f52e: Request failed: <urlopen error EOF occurred in violation of protocol (_ssl.c:590)>

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************************************************************
to retry, use: --limit @/home/labor/site.retry

node1 : ok=6 changed=1 unreachable=0 failed=1

rhim commented

The only workable solution we found to this problem before was to cache the docker key in our installation. This key is most likely not going to change for a while.