When you work with vSphere Lifecycle Manager baselines, an update stands for all patches, extensions, and upgrades that you can apply with vSphere Lifecycle Manager baselines. The compliance status of the updates in the baselines and baseline groups that you attach to objects in your inventory is calculated after you check the compliance of the target object.
The compliance statuses of the updates in a baseline define the overall compliance status of that baseline. For more information about baseline compliance statuses, see Compliance Statuses of ESXi Hosts, Baselines, and Baseline Groups.
- Conflict
- The update conflicts with either an existing update on the host or another update in the vSphere Lifecycle Manager depot. vSphere Lifecycle Manager reports the type of conflict. A conflict does not indicate any problem on the target object. It just means that the current baseline selection is in conflict. You can perform compliance checks, remediation, and staging operations. In most cases, you must resolve the conflict.
- Conflicting New Module
- The host update is a new module that provides software for the first time, but it is in conflict with either an existing update on the host or another update in the vSphere Lifecycle Manager depot. vSphere Lifecycle Manager reports the type of conflict. A conflict does not indicate any problem on the target object. It just means that the current baseline selection is in conflict. You can perform scan, remediation, and staging operations. In most cases, you must resolve the conflict.
- Incompatible Hardware
- The hardware of the selected object is incompatible or has insufficient resources to support the update. For example, when you perform a host upgrade scan against a 32-bit host or if a host has insufficient RAM.
- Installed
- The update is installed on the target object and no further user action is required.
- Missing
- The update is applicable to the target object, but it is not yet installed. You must perform a remediation on the target object with this update, so that the update becomes compliant.
- Missing Package
- The metadata for the update is in the depot, but the corresponding binary payload is missing. The reasons can be that the product might not have an update for a given locale; the vSphere Lifecycle Manager depot is corrupt, and vSphere Lifecycle Manager no longer has Internet access to download updates; or you have manually deleted an upgrade package from the vSphere Lifecycle Manager depot.
- New Module
- The update is a new module. An update with this compliance status cannot be installed when it is part of a host patch baseline. When it is part of a host extension baseline, the new module status indicates that the module is missing on the host and can be provisioned by remediation. The compliance status of the baseline depends on the type of baseline containing the update with the New Module status. If the baseline is a host patch baseline, the overall status of the baseline is compliant. If the baseline is a host extension baseline, the overall status of the baseline is non-compliant.
- Not Applicable
-
The update is not applicable to the target object. A patch might have the not applicable compliance status for one of the following reasons:
- There are other patches in the vSphere Lifecycle Manager depot that obsolete this patch.
- The update does not apply to the target object.
- Not Installable
- The update cannot be installed. The compliance check might succeed, but the remediation of the target object cannot be performed.
- Obsoleted By Host
- This compliance status is mainly applicable to patches. The target object has a newer version of the patch. For example, if a patch has multiple versions, after you apply the latest version to the host, the earlier versions of the patch have the Obsoleted By Host compliance status.
- Staged
- This compliance status applies to host patches and host extensions. It indicates that the update is copied from the vSphere Lifecycle Manager depot to the host, but it is not yet installed. Staged compliance status might occur only when you check the compliance status of hosts running ESXi 6.5 and later.
- Unknown
- A patch is in the unknown state for a target object until vSphere Lifecycle Manager successfully scans the object. A scan might not succeed if the target object is of an unsupported version, if vSphere Lifecycle Manager lacks metadata, or if the patch metadata is corrupt.
- Unsupported Upgrade
- The upgrade path is not supported. For example, the current hardware version of the virtual machine is later than the latest version supported by the host.
