Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
incorrect path used only during synchronize task on FreeBSD #602
Please drag-drop large logs as text file attachments.
Feel free to write an issue in your preferred format, however if in doubt, use
All hundereds of preceding tasks in other roles & plays run perfectly -- except this one -- which is doing a simple rsync. For some reason the selected path is not correct, it should be:
--- - name: THIS WORKS | push out pkg build lists copy: src: "files/server.pkg" dest: "/usr/local/etc/poudriere.d/server.pkg" notify: poudriere | build tags: - build_pkgs - poudriere - pkg - name: THIS FAILS | push out port options synchronize: src: "files/poudriere.d/options/" dest: "/usr/local/etc/poudriere.d/options/" delete: yes recursive: yes notify: poudriere | build tags: - build_pkgs
Is this the most descriptive part of the failure?
Did the job hang after that, or did it print some other kind of exception?
My immediate suspicion is an internal problem with handling variables -- synchronize is a little special because it is an action plugin.
Do you have anything like
Also do you have
I'm trying to get the huge
hi David, this isn't urgent (I leave for a month's holiday this week) but seems curious - mitogen has IIRC always failed on this 1 role in all my plays.
Yep that line is the weird one, the path should be
A non-mitogen run shows this:
the base64-coded string appears to be this:
The base64'd chunk is the "first stage", it's possibly the ugliest trick in the library :)
I'm not looking at this just now, but there are at least two interesting things
Will dig into this sometime tomorrow. Thanks for reporting!
I think I can see what's happening. It does not relate to the target machine at all, but since you are running it on FreeBSD also, it relates to the local machine.
The synchronize plug-in uses
It seems hostvars is being used to fetch
The problem was the same as another bug buried somewhere in the tickets :) This fix also benefits
This is now on the master branch and will make it into the next release. To be updated when a new release is made, subscribe to https://networkgenomics.com/mail/mitogen-announce/
Thanks for reporting this!