Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Step "sync the remote host with code from the remote repository" fails with "Connection refused" #14489

Closed
php-coder opened this issue Jun 6, 2017 · 3 comments
Assignees
Labels
component/internal-tools kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1

Comments

@php-coder
Copy link
Contributor

PLAY [sync the remote host with code from the remote repository] ***************

TASK [Gathering Facts] *********************************************************
fatal: [172.18.6.252]: UNREACHABLE! => {
    "changed": false, 
    "generated_timestamp": "2017-06-06 07:26:56.594043", 
    "msg": "Failed to connect to the host via ssh: ssh: connect to host 172.18.6.252 port 22: Connection refused\r\n", 
    "unreachable": true
}

Seen here: https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_check/2832/console

CC @stevekuznetsov

@php-coder php-coder added the kind/test-flake Categorizes issue or PR as related to test flakes. label Jun 6, 2017
@stevekuznetsov
Copy link
Contributor

The probe for SSH connectivity was successful, so this looks like an AWS flake :\

TASK [aws-up : wait for SSH to be available] ***********************************
task path: /var/lib/jenkins/origin-ci-tool/54f1755641e07ff2be4a3812a9a5937eef8b697c/lib/python2.7/site-packages/oct/ansible/oct/playbooks/provision/roles/aws-up/tasks/main.yml:172
ok: [localhost] => {
    "changed": false, 
    "elapsed": 240, 
    "generated_timestamp": "2017-06-06 07:26:55.130310", 
    "path": null, 
    "port": 22, 
    "search_regex": null, 
    "state": "started"
}

@pweil-
Copy link
Contributor

pweil- commented Jun 8, 2017

I suppose we could retry. Please close if this isn't something we're going to fix

@stevekuznetsov
Copy link
Contributor

Yeah, this is just weirdness in AWS -- I've taken all the steps I can think of on the Ansible side of things for provisioning and connecting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/internal-tools kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1
Projects
None yet
Development

No branches or pull requests

3 participants