Project

Profile

Help

Task #8025

Check docker auth issues using empty machine

Added by Mark Zaslavskiy over 4 years ago. Updated over 4 years ago.

Status:
Won't fix
Priority:
High
Category:
mdbci features
Sprint/Milestone:
Start date:
14.03.2017
Due date:
% Done:

0%

Estimated time:
Target branch:
Test scenario:

Description

- Проверить почему машины с докером не проходят аутентификацию. (Саша проверить докер на AWS)(создать задачу)

History

#1 Updated by Mark Zaslavskiy over 4 years ago

09:54] 
timofey.turenko в инструкции https://github.com/OSLL/mdbci/blob/integration/PREAPARATION_FOR_MDBCI.md похоже баг: отсутствует строка %sudo ALL=(root) NOPASSWD: VAGRANT_EXPORTS_ADD, VAGRANT_NFSD_CHECK, VAGRANT_NFSD_START, VAGRANT_NFSD_APPLY, VAGRANT_EXPORTS_REMOVE, VAGRANT_EXPORTS_COPY

[09:54] 
добавил ее и докер стал работать, но другая проблема:

[09:55] 
INFO: > node_000: Auto-generating node name for Chef...
INFO: > node_000: Creating the container...
INFO: node_000: Name: local_test_node_000_1489473762
INFO: node_000: Image: centos_7_docker
INFO: node_000: Cmd: /usr/sbin/init
INFO: node_000: Volume: /home/turenko/build-scripts/test-setup-scripts/cnf:/home/vagrant/cnf_templates
INFO: node_000: Volume: /home/turenko/mdbci/local_test:/vagrant
INFO: node_000: Volume: /home/turenko/mdbci/recipes/cookbooks:/tmp/vagrant-chef/0d49f9d8e3fef4b5d46dd50d6252a423/cookbooks
INFO: node_000: Volume: /home/turenko/mdbci/local_test:/tmp/vagrant-chef/c54a8fb8584e033c30d9721db58b3249/roles
INFO: node_000: Port: 127.0.0.1:2222:22
INFO: node_000:
INFO: node_000: Container created: 8423319ed2d59132
INFO: > node_000: Starting container...
INFO: > node_000: Waiting for machine to boot. This may take a few minutes...
INFO: node_000: SSH address: 172.17.0.2:22
INFO: node_000: SSH username: vagrant
INFO: node_000: SSH auth method: private key
INFO: node_000: Warning: Authentication failure. Retrying...
INFO: node_000: Warning: Authentication failure. Retrying...
INFO: node_000: Warning: Authentication failure. Retrying...
INFO: node_000: Warning: Authentication failure. Retrying...
INFO: node_000: Warning: Authentication failure. Retrying...
INFO: node_000: Warning: Authentication failure. Retrying...
ERROR: Timed out while waiting for the machine to boot. This means that
ERROR: Vagrant was unable to communicate with the guest machine within
ERROR: the configured ("config.vm.boot_timeout" value) time period.
ERROR:
ERROR: If you look above, you should be able to see the error(s) that
ERROR: Vagrant had when attempting to connect to the machine. These errors
ERROR: are usually good hints as to what may be wrong.
ERROR:
ERROR: If you're using a custom box, make sure that networking is properly
ERROR: working and you're able to connect to the machine. It is a common
ERROR: problem that networking isn't setup properly in these boxes.
ERROR: Verify that authentication configurations are also setup properly,
ERROR: as well.
ERROR:
ERROR: If the box appears to be booting properly, you may want to increase
ERROR: the timeout ("config.vm.boot_timeout") value.
ERROR: Bringing up failed
ERROR: exit code 1
WARN: Checking for dead machines and checking Chef runs on machines
INFO: node_000 running (docker)
's password:

#2 Updated by Mark Zaslavskiy over 4 years ago

  • Assignee changed from Alexander Kaluzhny to Tatyana Berlenko

Ask Timofey - was this problem solved using recent discussion?

#3 Updated by Mark Zaslavskiy over 4 years ago

  • Status changed from New to Won't fix

Also available in: Atom PDF