{"action":"opened","issue":{"url":"https://api.github.com/repos/Juniper/ansible-junos-stdlib/issues/344","repository_url":"https://api.github.com/repos/Juniper/ansible-junos-stdlib","labels_url":"https://api.github.com/repos/Juniper/ansible-junos-stdlib/issues/344/labels{/name}","comments_url":"https://api.github.com/repos/Juniper/ansible-junos-stdlib/issues/344/comments","events_url":"https://api.github.com/repos/Juniper/ansible-junos-stdlib/issues/344/events","html_url":"https://github.com/Juniper/ansible-junos-stdlib/issues/344","id":309435983,"number":344,"title":"juniper_junos_software assumes that software image on Ansible host is 'uncorrupted' when checksums mismatch","user":{"login":"jnpr-bowen","id":27387465,"avatar_url":"https://avatars0.githubusercontent.com/u/27387465?v=4","gravatar_id":"","url":"https://api.github.com/users/jnpr-bowen","html_url":"https://github.com/jnpr-bowen","followers_url":"https://api.github.com/users/jnpr-bowen/followers","following_url":"https://api.github.com/users/jnpr-bowen/following{/other_user}","gists_url":"https://api.github.com/users/jnpr-bowen/gists{/gist_id}","starred_url":"https://api.github.com/users/jnpr-bowen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jnpr-bowen/subscriptions","organizations_url":"https://api.github.com/users/jnpr-bowen/orgs","repos_url":"https://api.github.com/users/jnpr-bowen/repos","events_url":"https://api.github.com/users/jnpr-bowen/events{/privacy}","received_events_url":"https://api.github.com/users/jnpr-bowen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-28T16:15:50Z","updated_at":"2018-03-28T16:15:50Z","closed_at":null,"author_association":"NONE","body":"While it may be true that file corruption occurs more often on the Juniper device, that alone is not reason enough to assume that the Ansible host file is not the one corrupted, which is the assumption with the way the task is implemented now. Without a comparison to a 'master checksum value', if both images exist during the playbook run, a mismatch in the checksums should result in the task failing. If a master checksum is added as an attribute of the task, several outcomes are available: file present on Ansible with mismatch to checksum but file not on device, fail; file present on Ansible and device with checksum mismatch on Ansible, proceed with warning; file present on Ansible and device with checksum mismatch on device, proceed as currently implemented, copy from Ansible to device."}}
{"actor":{"display_login":"jnpr-bowen"}}