Playbook build fails when deploying Matomo

[mjordan]

Building a Playbook has failed three times in a row for me, here:

ASK [Islandora-Devops.matomo : Expand Matomo.] ********************************
Wednesday 28 April 2021  12:51:47 -0700 (0:02:53.939)       0:32:22.014 *******
fatal: [default]: FAILED! => {"changed": false, "msg": "Failed to find handler for \"/var/www/html/piwik.zip\". Make sure the required command to extract the file is installed. Command \"/usr/bin/unzip\" could not handle archive. Command \"/usr/bin/tar\" could not handle archive."}

Both unzip and tar are available on the VM and execute normally.

I manually downloaded the zip file in question, https://builds.piwik.org/piwik-3.6.0.zip, and it unzips fine on the VM. The md5 of the file fetched by Ansible is 7334d8b1ec7ea74c07e1a9b9b73fd285, whereas the md5 of the manually (and sucessfully unzippable) file is 53c0580a185d8fe770590d6d0c909a78, so it would appear that the one downloaded within Ansible for deployment is corrupted. Size of good one is 19418053 bytes, size of bad one is 18421889, so maybe it's download is being intereupted?

I'll also point out that the latest version of Matomo is 4.2.1, so I'm wondering if we should upgrade to that version in the Ansible role.

Can someone try to build a fresh playbook to see if you can replicate what I'm describing?

[mjordan]

Build is now succeeding (not sure why) but now when I visit http://localhost:8000/matomo/ I am getting the following error:

@seth-shaw-unlv I think you've been building VMs for testing some PRs. What do you see when you visit http://localhost:8000/matomo/?

[seth-shaw-unlv]

The one I built 2 weeks ago is showing the same error. I was curious so I also spun up my performance testing image I built back in January and it shows the same error. I have an even older image I built back in mid-June which works fine... so the error crept in sometime between last June and January.

[mjordan]

OK, thanks, that's helpful, it's not just me. I resolved that error by deleting the matomo db and manually reinstalling. But I don't know what caused the initial error.

We probably should ship with Matomo is 4.2.1. I'll bring it up at today's tech call.

[mjordan]

2021-05-05 Tech Call consensus: update Matomo role to use 4.2.1 and see if that resolves the issue.