//Filled from a mail by @andrew to #together//
@Andrew is in the process of upgrading our various puppetmasters to modern versions. Before he takes the next step (https://gerrit.wikimedia.org/r/#/c/392172/) he is trying to get a grip on the current level of breakage so he can tell what (if anything) is broken additionally by the new parser.
As of November 19th, there are **11 VMs** in deployment-prep showing up with puppet errors or failures.
<snip>
-------
{icon check color=green} **deployment-cache-text04**
{icon check color=green} **deployment-cache-upload04**
```
Error: /usr/share/varnish/reload-vcl && (rm /var/tmp/reload-vcl-failed; true) returned 1 instead of one of [0]
Error: /Stage[main]/Cacheproxy::Instance_pair/Varnish::Instance[text-backend]/Exec[retry-load-new-vcl-file]/returns: change from notrun to 0 failed: /usr/share/varnish/reload-vcl && (rm /var/tmp/reload-vcl-failed; true) returned 1 instead of one of [0]
```
{icon check color=green} in hiera, they were missing key between_bytes_timeout to cache::app_def_be_opts
{icon cog} **deployment-changeprop**
{icon cog} **deployment-redis06**
Puppet got disabled as part of T179684
```
puppet disabled 'Testing changeprop-redis issue T179684'
Puppet has been disabled for 5248 minutes
```
**deployment-mx**
```
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: You can only use systemd resources on systems with systemd, got upstart at /etc/puppet/modules/systemd/manifests/init.pp:8 on node deployment-mx.deployment-prep.eqiad.wmflabs
```
-----
The following instances have outdated packages on the apt repo http://deployment-tin.deployment-prep.eqiad.wmflabs/repo . Most probably due to `deployment-phab` being broken.
The instance has been created on October 26th by @mmodell. It serves as an apt repo
**deployment-phab**
Can't log into this one; maybe it never finished building.
**deployment-tin**
Various apt/packaging dependency issues
**deployment-kafka-jumbo-1 and -2**
package dependency issues breaking apt