(resent as I forgot to send it to the submitter)
Hi Carlos,
I'm closing this bug as wontfix. The reason is that upstream has little
motivation of changing the behaviour, and there is a workaround available
(filtering out those message via syslog).
Regards,
Lee
Hi Carlos,
I'm closing this bug as wontfix. The reason is that upstream has little
motivation of changing the behaviour, and there is a workaround available
(filtering out those message via syslog).
Regards,
Lee
Control: tag -1 - moreinfo
On Sat, 12 Apr 2014 21:32:17 -0400 Harlan Lieberman-Berg
wrote:
> Upstream says that this functionality may have been added by no_log
> becoming a task parameter. Does this functionality solve your issue?
It does not solve mine.
The perfect solution for me would be a
On Sat, 12 Apr 2014 21:32:17 -0400 Harlan Lieberman-Berg
wrote:
> Hello Carlos,
>
> Upstream says that this functionality may have been added by no_log
> becoming a task parameter. Does this functionality solve your issue?
>
> Sincerely,
> --
> Harlan Lieberman-Berg
> ~hlieberman
I just real
tag 707275 +moreinfo
thanks
Hello Carlos,
Upstream says that this functionality may have been added by no_log
becoming a task parameter. Does this functionality solve your issue?
Sincerely,
--
Harlan Lieberman-Berg
~hlieberman
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debia
just a quick update on this bug. I forwarded it upstream as:
https://github.com/ansible/ansible/issues/5525#issuecomment-31738942
and created a git branch with the fix here:
https://github.com/ansible/ansible/pull/5552
Lets see if upstream likes it and pulls it in for 1.4.5/1.5 :)
--
To UNSUBS
Hi,
I forwarded this to https://github.com/ansible/ansible/issues/5525
Looks (from a quick look) not entirely straightforward, but I could be
wrong :)
Cheers,
Michael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm
tags 707275 + upstream
thanks
I'm not 100% sure that this bug shouldn't be set wontfix. There's a
balance here to be made between creating an audit trail on the system for
what ansible has done to it, and causing too much noise.
It seems to me that erring on the side of logging more audit inform
Package: ansible
Version: 1.1+dfsg-1
Severity: normal
When executing the ping module on server:
ansible servername -c ssh -m ping
It causes a log entry on the target server
# grep -r servername /var/log/
/var/log/messages:May 8 15:09:07 servername ansible-ping: Invoked with
data=None
/v
9 matches
Mail list logo