{"action":"created","issue":{"url":"https://api.github.com/repos/ansible/ansible/issues/35532","repository_url":"https://api.github.com/repos/ansible/ansible","labels_url":"https://api.github.com/repos/ansible/ansible/issues/35532/labels{/name}","comments_url":"https://api.github.com/repos/ansible/ansible/issues/35532/comments","events_url":"https://api.github.com/repos/ansible/ansible/issues/35532/events","html_url":"https://github.com/ansible/ansible/issues/35532","id":293046461,"node_id":"MDU6SXNzdWUyOTMwNDY0NjE=","number":35532,"title":"couldn't disable paramiko.transport verbose log in ansible log","user":{"login":"qduxiaoliang","id":16145711,"node_id":"MDQ6VXNlcjE2MTQ1NzEx","avatar_url":"https://avatars1.githubusercontent.com/u/16145711?v=4","gravatar_id":"","url":"https://api.github.com/users/qduxiaoliang","html_url":"https://github.com/qduxiaoliang","followers_url":"https://api.github.com/users/qduxiaoliang/followers","following_url":"https://api.github.com/users/qduxiaoliang/following{/other_user}","gists_url":"https://api.github.com/users/qduxiaoliang/gists{/gist_id}","starred_url":"https://api.github.com/users/qduxiaoliang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/qduxiaoliang/subscriptions","organizations_url":"https://api.github.com/users/qduxiaoliang/orgs","repos_url":"https://api.github.com/users/qduxiaoliang/repos","events_url":"https://api.github.com/users/qduxiaoliang/events{/privacy}","received_events_url":"https://api.github.com/users/qduxiaoliang/received_events","type":"User","site_admin":false},"labels":[{"id":562292166,"node_id":"MDU6TGFiZWw1NjIyOTIxNjY=","url":"https://api.github.com/repos/ansible/ansible/labels/affects_2.4","name":"affects_2.4","color":"ededed","default":false},{"id":785271699,"node_id":"MDU6TGFiZWw3ODUyNzE2OTk=","url":"https://api.github.com/repos/ansible/ansible/labels/bug","name":"bug","color":"fbca04","default":true},{"id":636352796,"node_id":"MDU6TGFiZWw2MzYzNTI3OTY=","url":"https://api.github.com/repos/ansible/ansible/labels/support:core","name":"support:core","color":"ededed","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-01-31T06:34:25Z","updated_at":"2018-06-10T04:06:22Z","closed_at":null,"author_association":"NONE","body":"<!---\r\nVerify first that your issue/request is not already reported on GitHub.\r\nAlso test if the latest release, and master branch are affected too.\r\n-->\r\n\r\n##### ISSUE TYPE\r\n<!--- Pick one below and delete the rest -->\r\n - Bug Report\r\n\r\n##### COMPONENT NAME\r\n<!---\r\nName of the module, plugin, task or feature\r\nDo not include extra details here, e.g. \"vyos_command\" not \"the network module vyos_command\" or the full path\r\n-->\r\nlog\r\n\r\n##### ANSIBLE VERSION\r\n<!--- Paste verbatim output from \"ansible --version\" between quotes below -->\r\n```\r\n[root@server]# ansible --version\r\nansible 2.4.2.0\r\n  config file = /etc/ansible/ansible.cfg\r\n  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']\r\n  ansible python module location = /usr/lib/python2.6/site-packages/ansible\r\n  executable location = /usr/bin/ansible\r\n  python version = 2.6.6 (r266:84292, Aug  9 2016, 06:11:56) [GCC 4.4.7 20120313 (Red Hat 4.4.7-17)]\r\n```\r\n\r\n##### CONFIGURATION\r\n<!---\r\nIf using Ansible 2.4 or above, paste the results of \"ansible-config dump --only-changed\"\r\nOtherwise, mention any settings you have changed/added/removed in ansible.cfg\r\n(or using the ANSIBLE_* environment variables).\r\n-->\r\n[root@sun kvm]# ansible-config dump --only-changed\r\nDEFAULT_FORCE_HANDLERS(/test/ansible.cfg) = False\r\nDEFAULT_GATHERING(/test/ansible.cfg) = explicit\r\nDEFAULT_LOG_PATH(/test/ansible.cfg) = /test/log.txt\r\nDEFAULT_REMOTE_USER(/test/ansible.cfg) = root\r\nDEFAULT_TIMEOUT(/test/ansible.cfg) = 30\r\nHOST_KEY_CHECKING(/test/ansible.cfg) = False\r\n\r\n##### OS / ENVIRONMENT\r\n<!---\r\nMention the OS you are running Ansible from, and the OS you are\r\nmanaging, or say \"N/A\" for anything that is not platform-specific.\r\nAlso mention the specific version of what you are trying to control,\r\ne.g. if this is a network bug the version of firmware on the network device.\r\n-->\r\n[root@server]# rpm -q redhat-release-server-6Server\r\nredhat-release-server-6Server-6.9.0.4.el6.x86_64\r\n\r\n##### SUMMARY\r\n<!--- Explain the problem briefly -->\r\nthere are lot of paramiko transport log in ansible log as below.\r\nthere is no configuration option to disable the paramiko transport log.\r\n\r\n+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\r\n2018-01-31 22:00:37,148 paramiko.transport starting thread (client mode): 0x2710b50L\r\n2018-01-31 22:00:37,153 paramiko.transport Connected (version 2.0, client OpenSSH_5.3)\r\n2018-01-31 22:00:37,155 paramiko.transport kex algos:['diffie-hellman-group-exchange-sha256', 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1', 'diffie-hellman-group1-sha1'] server key:['ssh-rsa', 'ssh-dss'] client encrypt:['aes192-ctr', 'aes256-ctr'] server encrypt:['aes192-ctr', 'aes256-ctr'] client mac:['hmac-sha1', 'hmac-ripemd160'] server mac:['hmac-sha1', 'hmac-ripemd160'] client compress:['none', 'zlib@openssh.com'] server compress:['none', 'zlib@openssh.com'] client lang:[''] server lang:[''] kex follows?False\r\n2018-01-31 22:00:37,155 paramiko.transport Ciphers agreed: local=aes256-ctr, remote=aes256-ctr\r\n2018-01-31 22:00:37,156 paramiko.transport using kex diffie-hellman-group1-sha1; server key type ssh-rsa; cipher: local aes256-ctr, remote aes256-ctr; mac: local hmac-sha1, remote hmac-sha1; compression: local none, remote none\r\n2018-01-31 22:00:37,164 paramiko.transport starting thread (client mode): 0x270eb50L\r\n2018-01-31 22:00:37,170 paramiko.transport Connected (version 2.0, client OpenSSH_5.3)\r\n2018-01-31 22:00:37,173 paramiko.transport kex algos:['diffie-hellman-group-exchange-sha256', 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1', 'diffie-hellman-group1-sha1'] server key:['ssh-rsa', 'ssh-dss'] client encrypt:['aes192-ctr', 'aes256-ctr'] server encrypt:['aes192-ctr', 'aes256-ctr'] client mac:['hmac-sha1', 'hmac-ripemd160'] server mac:['hmac-sha1', 'hmac-ripemd160'] client compress:['none', 'zlib@openssh.com'] server compress:['none', 'zlib@openssh.com'] client lang:[''] server lang:[''] kex follows?False\r\n2018-01-31 22:00:37,173 paramiko.transport Ciphers agreed: local=aes256-ctr, remote=aes256-ctr\r\n2018-01-31 22:00:37,173 paramiko.transport using kex diffie-hellman-group1-sha1; server key type ssh-rsa; cipher: local aes256-ctr, remote aes256-ctr; mac: local hmac-sha1, remote hmac-sha1; compression: local none, remote none\r\n2018-01-31 22:00:37,282 paramiko.transport Switch to new keys ...\r\n2018-01-31 22:00:37,286 paramiko.transport Trying discovered key 3720965f1775ee68d2b94b21919f7df2 in /root/.ssh/id_rsa\r\n2018-01-31 22:00:37,301 paramiko.transport Switch to new keys ...\r\n2018-01-31 22:00:37,304 paramiko.transport Trying discovered key 3720965f1775ee68d2b94b21919f7df2 in /root/.ssh/id_rsa\r\n2018-01-31 22:00:37,322 paramiko.transport userauth is OK\r\n2018-01-31 22:00:37,340 paramiko.transport userauth is OK\r\n2018-01-31 22:00:37,644 paramiko.transport Auth banner: WARNING: Anyone accessing or attempting to access the IS without authorisation runs the risk of a one-year prison sentence and a fine of 15,244 Euros (New Criminal Code - Article 323-1)\r\n\r\n2018-01-31 22:00:37,644 paramiko.transport Authentication (publickey) successful!\r\n2018-01-31 22:00:37,645 paramiko.transport [chan 1] Max packet in: 34816 bytes\r\n2018-01-31 22:00:37,651 paramiko.transport [chan 1] Max packet out: 32768 bytes\r\n2018-01-31 22:00:37,652 paramiko.transport Secsh channel 1 opened.\r\n2018-01-31 22:00:37,654 paramiko.transport [chan 1] Sesch channel 1 request ok\r\n2018-01-31 22:00:37,657 paramiko.transport Auth banner: WARNING: Anyone accessing or attempting to access the IS without authorisation runs the risk of a one-year prison sentence and a fine of 15,244 Euros (New Criminal Code - Article 323-1)\r\n\r\n2018-01-31 22:00:37,657 paramiko.transport Authentication (publickey) successful!\r\n2018-01-31 22:00:37,662 paramiko.transport [chan 1] Max packet in: 34816 bytes\r\n2018-01-31 22:00:37,667 paramiko.transport [chan 1] EOF received (1)\r\n2018-01-31 22:00:37,668 paramiko.transport [chan 2] Max packet in: 34816 bytes\r\n2018-01-31 22:00:37,668 paramiko.transport [chan 1] EOF sent (1)\r\n2018-01-31 22:00:37,669 paramiko.transport [chan 2] Max packet out: 32768 bytes\r\n2018-01-31 22:00:37,669 paramiko.transport Secsh channel 2 opened.\r\n2018-01-31 22:00:37,681 paramiko.transport [chan 1] Max packet out: 32768 bytes\r\n2018-01-31 22:00:37,681 paramiko.transport Secsh channel 1 opened.\r\n2018-01-31 22:00:37,696 paramiko.transport [chan 1] Sesch channel 1 request ok\r\n2018-01-31 22:00:37,711 paramiko.transport [chan 2] Sesch channel 2 request ok\r\n2018-01-31 22:00:37,720 paramiko.transport [chan 1] EOF received (1)\r\n2018-01-31 22:00:37,721 paramiko.transport [chan 1] EOF sent (1)\r\n2018-01-31 22:00:37,721 paramiko.transport [chan 2] Max packet in: 34816 bytes\r\n2018-01-31 22:00:37,750 paramiko.transport [chan 2] EOF received (2)\r\n2018-01-31 22:00:37,751 paramiko.transport [chan 2] EOF sent (2)\r\n2018-01-31 22:00:37,752 paramiko.transport [chan 3] Max packet in: 34816 bytes\r\n2018-01-31 22:00:37,762 paramiko.transport [chan 2] Max packet out: 32768 bytes\r\n2018-01-31 22:00:37,762 paramiko.transport Secsh channel 2 opened.\r\n2018-01-31 22:00:37,787 paramiko.transport [chan 2] Sesch channel 2 request ok\r\n2018-01-31 22:00:37,793 paramiko.transport [chan 3] Max packet out: 32768 bytes\r\n2018-01-31 22:00:37,793 paramiko.transport Secsh channel 3 opened.\r\n2018-01-31 22:00:37,793 paramiko.transport Secsh channel 3 opened.\r\n2018-01-31 22:00:37,816 paramiko.transport [chan 2] EOF received (2)\r\n2018-01-31 22:00:37,818 paramiko.transport [chan 2] EOF sent (2)\r\n2018-01-31 22:00:37,818 paramiko.transport [chan 3] Sesch channel 3 request ok\r\n2018-01-31 22:00:37,819 paramiko.transport [chan 3] Max packet in: 34816 bytes\r\n2018-01-31 22:00:37,845 paramiko.transport.sftp [chan 3] Opened sftp connection (server version 3)\r\n2018-01-31 22:00:37,845 paramiko.transport.sftp [chan 3] open('/root/.ansible/tmp/ansible-tmp-1517407237.14-32002567524013/command.py', 'wb')\r\n2018-01-31 22:00:37,847 paramiko.transport.sftp [chan 3] open('/root/.ansible/tmp/ansible-tmp-1517407237.14-32002567524013/command.py', 'wb') -> 00000000\r\n2018-01-31 22:00:37,852 paramiko.transport.sftp [chan 3] close(00000000)\r\n2018-01-31 22:00:37,856 paramiko.transport.sftp [chan 3] stat('/root/.ansible/tmp/ansible-tmp-1517407237.14-32002567524013/command.py')\r\n2018-01-31 22:00:37,859 paramiko.transport [chan 4] Max packet in: 34816 bytes\r\n2018-01-31 22:00:37,860 paramiko.transport [chan 4] Max packet out: 32768 bytes\r\n2018-01-31 22:00:37,860 paramiko.transport [chan 3] Max packet out: 32768 bytes\r\n2018-01-31 22:00:37,860 paramiko.transport Secsh channel 4 opened.\r\n2018-01-31 22:00:37,860 paramiko.transport Secsh channel 3 opened.\r\n\r\n\r\n##### STEPS TO REPRODUCE\r\n<!---\r\nFor bugs, show exactly how to reproduce the problem, using a minimal test-case.\r\nFor new features, show how the feature would be used.\r\n-->\r\ncreate a ansible.cfg file and set log_path option as below:\r\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++\r\n[defaults]\r\nhost_key_checking=False\r\nlog_path=log.txt\r\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++\r\n\r\n<!--- Paste example playbooks or commands between quotes below -->\r\n```yaml\r\nansible-playbook -c paramiko -i hosts test.yml\r\n```\r\n\r\n<!--- You can also paste gist.github.com links for larger files -->\r\n\r\n##### EXPECTED RESULTS\r\n<!--- What did you expect to happen when running the steps above? -->\r\nthere should be a configuration to disable those verbose paramiko transport log\r\n\r\n##### ACTUAL RESULTS\r\n<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->\r\n\r\n<!--- Paste verbatim command output between quotes below -->\r\n```\r\n\r\n```\r\n"},"comment":{"url":"https://api.github.com/repos/ansible/ansible/issues/comments/396018754","html_url":"https://github.com/ansible/ansible/issues/35532#issuecomment-396018754","issue_url":"https://api.github.com/repos/ansible/ansible/issues/35532","id":396018754,"node_id":"MDEyOklzc3VlQ29tbWVudDM5NjAxODc1NA==","user":{"login":"Akasurde","id":633765,"node_id":"MDQ6VXNlcjYzMzc2NQ==","avatar_url":"https://avatars1.githubusercontent.com/u/633765?v=4","gravatar_id":"","url":"https://api.github.com/users/Akasurde","html_url":"https://github.com/Akasurde","followers_url":"https://api.github.com/users/Akasurde/followers","following_url":"https://api.github.com/users/Akasurde/following{/other_user}","gists_url":"https://api.github.com/users/Akasurde/gists{/gist_id}","starred_url":"https://api.github.com/users/Akasurde/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Akasurde/subscriptions","organizations_url":"https://api.github.com/users/Akasurde/orgs","repos_url":"https://api.github.com/users/Akasurde/repos","events_url":"https://api.github.com/users/Akasurde/events{/privacy}","received_events_url":"https://api.github.com/users/Akasurde/received_events","type":"User","site_admin":false},"created_at":"2018-06-10T04:06:22Z","updated_at":"2018-06-10T04:06:22Z","author_association":"MEMBER","body":"@qduxiaoliang Could you please let us know if #35565 works for you, so that we can mark this bug as closed ? \r\n\r\nneeds_info"}}
{"actor":{"display_login":"Akasurde"}}