Track the success of upgrades
We should begin to collect statistics on how many of our upgrades succeed or fail. This is important for us to measure our success rates across releases, catch potentially uncommon issues, as well as allow us to react sooner in the event of a wide spread problem.
Possible options:
- Save hash of the gitlab.rb when successful reconfigure. If an error occurs during a future reconfigure with a config that was previously (confirmed by the hash) report the cause of the issue. (Deprecation, unknown, etc.)
- If a package fails to upgrade during the package installation phase, report that issue upstream as well.