When verifying an upgrade, the verification job can sometimes detect particular action items called "upgrade checks". These checks are items that the Delphix Engine is not capable of fixing on its own, and require customer and/or Delphix support action. Every upgrade check that appears must be resolved, ignored, or acknowledged before upgrade can proceed.
Upgrade Severities Checks
|WARNING||These checks indicate problems that are local to some objects on the Delphix Engine, but the overall engine can continue running. For example, WARNING checks may indicate a problem with the configuration of a particular Windows environment, and indicate that if an upgrade occurs, that environment will not function properly.|
|CRITICAL||These checks indicate a potential problem post-upgrade with the Delphix Engine. The Delphix Engine cannot be upgraded while CRITICAL checks are present; it is likely that the engine will fail to upgrade or break catastrophically post-upgrade.|
The following is a list of checks that have been added to the Delphix Engine:
Replication (WARNING) - It indicates that your Delphix Engine has replication set up as either a target or source. Delphix Engines can only perform replication to engines on the same version, so it is recommended to upgrade all engines in a replication group at the same time.
OS tunable settings (CRITICAL) - Upgrade verification checks that only a certain set of operating system tunables have been adjusted. If tunable settings not on this acceptable list have been changed, please contact Delphix support.
Hotfix (CRITICAL) - Upgrade verification checks if any hotfixes have been applied to the Delphix Engine, and if any exist that are not resolved in the Upgrade version, this check will generate a Critical result. In this scenario, the Engine may still be upgraded, but we ask that you contact Delphix support to assist in addressing the check.
Snapshot directory visible (CRITICAL) - This is an internal Delphix Engine problem that Delphix support can resolve for our customers.
An Upgrade check can result in multiple check results. Check results are essentially a to-do list of action items required before performing an upgrade. For example, the OS Tunables will create one line item in the UI for each present tunable that is not on our acceptable list. There are three actions that can be performed on each check result.
Upgrade Check Actions
|resolve||You have taken the action necessary to solve the problem and complete the action item. Marking a result as resolved means that the customer believes the check result indicated will no longer be a problem. The next verification run will check the result again, but if it is fixed will not create any new check results.|
|ignore||You have no intention of fixing the problem indicated by the check result. Future verification runs will not generate that check result again if it is present. CRITICAL severity checks cannot be ignored.|
|reset||Checks that have been ignored, resolved, or acknowledged can be reset back to the unresolved state. This might be used if you desire to fix a check that was previously ignored and add it back to the list of action items.|