Apt Repository fails to update cache

[stonier]

Currently broken the first time you run groot-ansible extras/chrome on 18.04. It will try to update the cache:

- name: add apt-repository
  apt_repository:
    repo: "deb [arch=amd64] {{ chrome_apt_uri }} stable main"
    state: present
    filename: google-chrome
    update_cache: yes  # only triggers if there was a change to the repos
  become: yes

Error report:

The full traceback is:
Traceback (most recent call last):
  File "/tmp/ansible_jGGipi/ansible_module_apt_repository.py", line 551, in <module>
    main()
  File "/tmp/ansible_jGGipi/ansible_module_apt_repository.py", line 543, in main
    cache.update()
  File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 588, in update
    raise FetchFailedException()
apt.cache.FetchFailedException

fatal: [localhost]: FAILED! => {
    "changed": false, 
    "module_stderr": "Traceback (most recent call last):\n  File \"/tmp/ansible_jGGipi/ansible_module_apt_repository.py\", line 551, in <module>\n    main()\n  File \"/tmp/ansible_jGGipi/ansible_module_apt_repository.py\", line 543, in main\n    cache.update()\n  File \"/usr/lib/python2.7/dist-packages/apt/cache.py\", line 588, in update\n    raise FetchFailedException()\napt.cache.FetchFailedException\n", 
    "module_stdout": "", 
    "msg": "MODULE FAILURE", 
    "rc": 1
}

Likely ansible bug? See the stack overflow answer here.

[stonier]

Workaround: re-run commands, since the repository file will be there second time around, it won't flail trying to update the cache.

Testing: Possibly could see if it works with a later version using the virtualenv installed ansible.