Ansible Said to report this

[Brian Richards]

TASK: [name | Copying Build to local host] ************************************

warning: md5sum command failed unusually, please report this to the list so it can be fixed

command: [u'(/usr/bin/md5sum /var/lib/jenkins/jobs/name_qa/workspace/rel/name.tar.gz 2>/dev/null)', u'(/sbin/md5sum -q /var/lib/jenkins/jobs/name_qa/workspace/rel/name.tar.gz 2>/dev/null)', u'(/usr/bin/digest -a md5 /var/lib/jenkins/jobs/name_qa/workspace/rel/name.tar.gz 2>/dev/null)', u'(/sbin/md5 -q /var/lib/jenkins/jobs/name_qa/workspace/rel/name.tar.gz 2>/dev/null)', u'(/usr/bin/md5 -n /var/lib/jenkins/jobs/name_qa/workspace/rel/name.tar.gz 2>/dev/null)', u'(/bin/md5 -q /var/lib/jenkins/jobs/name_qa/workspace/rel/icda.tar.gz 2>/dev/null)', u'(/usr/bin/csum -h MD5 /var/lib/jenkins/jobs/name_qa/workspace/rel/name.tar.gz 2>/dev/null)', u'(/bin/csum -h MD5 /var/lib/jenkins/jobs/name_qa/workspace/rel/name.tar.gz 2>/dev/null)']

----

output: {'stdout': '', 'stderr': '', 'rc': 255}

Here is what I was trying to run:

- name: Copying Build to local host

  fetch: src=/var/lib/jenkins/jobs/name_{{ my_environment }}/workspace/rel/name.tar.gz dest=/tmp/{{my_environment}}/ flat=yes fail_on_missing=yes

  delegate_to: hostvars[groups['buildservers'][0]]

Basically I was just trying to copy a build from our build server to my local box while running the name task.

I even tried to turn off the validate_md5 flag and I still got the same error.

FYI I'm using ansible 1.5 with a mac host and a centos source and a rhel target.

[Michael DeHaan]

Thanks Brian.

Ansible 1.5 is an out of date version of Ansible.  In particular, there are security fixes you want to be using on the 1.6 line, and the current version is 1.6.10.

Please see if you see this same problem in 1.6.10, and please supply version specifics about your RHEL host.

However, I haven't /ever/ seen an md5 error from a RHEL host, so this may require some further checking.

The md5 validation flag on fetch is different than the general md5 operations ansible uses to decide if certain files need to be transferred and so on.

It may be true there is a error down the path where flat=yes and fail_on_missing are added, so if you can still reproduce this on 1.6.10 or the development branch, please let us know and we can try to reproduce this. 

If that situation is in fact true, filing a ticket at github.com/ansible/ansible would be ideal.

Thanks!

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/79aa66cc-e944-4ac4-b247-9d954d932bfa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stephen John Smoogen]

On Aug 2, 2014 7:48 AM, "Michael DeHaan" <mic...@ansible.com> wrote:
>
> Thanks Brian.
>
> Ansible 1.5 is an out of date version of Ansible.  In particular, there are security fixes you want to be using on the 1.6 line, and the current version is 1.6.10.
>
> Please see if you see this same problem in 1.6.10, and please supply version specifics about your RHEL host.
>
> However, I haven't /ever/ seen an md5 error from a RHEL host, so this may require some further checking.
>

It can happen if the host is in FIPS mode. Not sure this is the case or not.

[Brian Richards]

FYI I updated ansible to 1.6.9 and it appears to be working as expected.  There must have been a bug in the past that you guys accidentally fixed.  Thanks for the quick response and recommendation..  

[Michael DeHaan]

"accidentally fixed"

That didn't sound nice :)

--

You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/cdd58886-0f22-47ab-860b-cf087b6917f8%40googlegroups.com.

[Gmail]

Accidental fixes are the best fixes!

You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/mw6NhqhriKU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.

To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgyrCL11-MRnQ1sc9tyQ8sY%2BbOFyfsYWwi9rSfBuZ0SNhg%40mail.gmail.com.

[Michael DeHaan]

I don't think a fix was accidental in the least but I do not claim encyclopedic knowledge of 11,467 different commits and when they were applied :)

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/35394479-E0F5-4884-997E-99B6C8B66BE8%40gmail.com.