follow task renames

The list of affected hosts and packages can be inspected with the

following [fabric](howto/fabric) command:

    fab -H pauli.torproject.org host.all-pending-upgrades

    fab -H pauli.torproject.org fleet.pending-upgrades

Note that this will *also* catch hosts that have pending upgrade that

*may* be upgraded automatically by unattended-upgrades, as it doesn't

check for alerts, but for the metric directly. You can use the

`--query` parameter to restrict to the alerting hosts instead:

    fab -H pauli.torproject.org host.all-pending-upgrades --query='ALERTS{alertname="PackagesPendingTooLong",alertstate="firing"}'

    fab -H pauli.torproject.org fleet.pending-upgrades --query='ALERTS{alertname="PackagesPendingTooLong",alertstate="firing"}'

Look at the list of packages to be upgraded, and consider upgrading

them manually, with Cumin (see below), or individually, by logging

To check the entire fleet, run this command in [Fabric](howto/fabric):

    fab host.all-pending-restarts

    fab fleet.pending-restarts

Packages are blocked from upgrades when they cause significant

breakage during an upgrade run, enough to cause an outage and/or