Hi,
Monica wrote:
> Thank you for sharing the same, however, I have already
> checked this article.
I was simply quoting the article which Will kindly shared to
mention that ProxyJump / -J might be a simpler method, even
within ansible_ssh_common_args.
[I reformatted some of the text you wrote a
Will McDonald wrote:
> https://www.jeffgeerling.com/blog/2022/
> using-ansible-playbook-ssh-bastion-jump-host
Odd that uses ProxyCommand in `ansible_ssh_common_args` and
not the far simpler ProxyJump, which it does mention in the
~/.ssh/config method. The `-J` shortcut for that is even
better.
P
Ki-Hyun Sung wrote:
Thanks a lot for that Todd!
The export=yes worked for me.
So does it mean that now I can take the resultant noarch rpm and use
it to install ansible on other centos boxes, in a docker container
etc?
I would like to think so, but I can't vouch for the build process.
It'
Toshio Kuratomi wrote:
This looks like you aren't getting the tarballs from the official source:
https://releases.ansible.com/ansible/
This still happens with the offical tarballs. The 'make rpm' target
does not work as documented due to numerous issues, which I tried to
document in my reply
I wrote:
I needed to install the following packages to build:
asciidoc
epel-release
python2-devel
python2-jinja2
BTW, python2-jinja2 was a typo. It's just python-jinja2 in EL-7, as
listed below.
python-jinja2
python-setuptools
python-yaml
rpm-build
--
Todd
~~
Hi,
Ki-Hyun Sung wrote:
I am trying to create my own Ansible rpm from the tarball.
I am on Centos 7, with asciidoc, epel-release and rpmbuild packages
installed.
However I get this error when I try to 'make rpm' from the root of the
extracted tarball (ansible version 2.4.0.0)
*error: line
Jacob Weber wrote:
Just to clarify -- I was seeing the same results as Kevin, not Todd.
Removing "pipelining = True" from my config fixed the problem.
I've since updated to 1.7.2 from epel-testing and I see the same
results as you and Kevin. I've disabled pipelining as well for now,
but it'
Kevin Fenzi wrote:
On Wed, 15 Oct 2014 16:07:42 -0700
Michael DeHaan wrote:
"I think this is a bug, has anyone tested this ?"
Sounds like this should be reported with RHEL, definitely.
Please do and post the bugzilla here if you can.
While we could add special code to say "don't try CP on
Dag Wieers wrote:
As some of you may know, Red Hat backported the ControlPersist
functionality to the OpenSSH version that ships with RHEL6.
This is terrific since RHEL users can now use this technique to
speed up Ansible.
However, after some testing it seems to fail for the very first
conn
