From: Loic Dachary <loic@dachary.org>
To: Zack Cerza <zack@redhat.com>, Andrew Schoen <aschoen@redhat.com>
Cc: Dan Mick <dmick@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: ansible task progress
Date: Wed, 08 Jul 2015 02:48:47 +0200 [thread overview]
Message-ID: <559C736F.1030005@dachary.org> (raw)
In-Reply-To: <559C719C.8010707@dachary.org>
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
Hi again,
The next problem was worked around with
ansible_user: ubuntu
and then I got
http://integration.ceph.dachary.org:8081/ubuntu-2015-07-08_00:36:46-noop-master---basic-openstack/4/
2015-07-08 00:41:31,538.538 INFO:teuthology.task.ansible.out:failed: [ovh226240.teuthology] => (item=ansible_user_ssh_keys) => {"fa\
iled": true, "item": "ansible_user_ssh_keys"}
2015-07-08 00:41:31,539.539 INFO:teuthology.task.ansible.out:
msg: invalid key specified: ansible_user_ssh_keys
hopefully that's enough clues for you to figure out a real fix. Sorry I don't know enough to propose a proper patch.
Cheers
On 08/07/2015 02:41, Loic Dachary wrote:
> Hi Zack & Andrew,
>
> With Dan's help we hacked passed the sudo problem with:
>
> cat > /tmp/ansible.yaml <<EOF
> overrides:
> ansible.cephlab:
> branch: wip-fix-defaults
> vars:
> ansible_sudo: true
> interactive-on-error: true
> EOF
>
> teuthology-suite --machine-type openstack --suite-dir $(pwd)/teuthology/test/integration --suite noop /tmp/ansible.yaml
>
> with full logs at
>
> http://integration.ceph.dachary.org:8081/ubuntu-2015-07-08_00:31:07-noop-master---basic-openstack/3/
>
> Cheers
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-07-08 0:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 0:41 ansible task progress Loic Dachary
2015-07-08 0:48 ` Loic Dachary [this message]
2015-07-08 1:11 ` Dan Mick
2015-07-08 14:59 ` Andrew Schoen
2015-07-08 18:05 ` Loic Dachary
2015-07-08 20:35 ` Andrew Schoen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=559C736F.1030005@dachary.org \
--to=loic@dachary.org \
--cc=aschoen@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dmick@redhat.com \
--cc=zack@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.