thumbor1002 runs 2.40.20 when the rest of the cluster is on the standard Debian Stretch version (2.40.16).
This leads to rendering inconsistencies depending on which thumbor server renders a given SVG thumbnail (see parent task).
Is that an upgrade that's being tested and not completed? It seems like all thumbor servers are seeing the potential upgrade, which @jijiki uploaded in December:
gilles@thumbor1002:~$ apt-cache policy librsvg2-bin
librsvg2-bin:
Installed: 2.40.20-3+wmf1+stretch1
Candidate: 2.40.20-3+wmf1+stretch1
Version table:
*** 2.40.20-3+wmf1+stretch1 1001
1001 http://apt.wikimedia.org/wikimedia stretch-wikimedia/component/thumbor amd64 Packages
100 /var/lib/dpkg/status
2.40.16-1+b1 500
500 http://mirrors.wikimedia.org/debian stretch/main amd64 Packages
gilles@thumbor2001:~$ apt-cache policy librsvg2-bin
librsvg2-bin:
Installed: 2.40.16-1+b1
Candidate: 2.40.20-3+wmf1+stretch1
Version table:
2.40.20-3+wmf1+stretch1 1001
1001 http://apt.wikimedia.org/wikimedia stretch-wikimedia/component/thumbor amd64 Packages
*** 2.40.16-1+b1 500
500 http://mirrors.wikimedia.org/debian stretch/main amd64 Packages
100 /var/lib/dpkg/status