Several common content issues may arise when using vRealize Suite Lifecycle Manager.

  • When transferring a customization spec between vCenter servers, the password fields cannot be decrypted by the target. This causes deployments that depend on custom specs with passwords to fail. You can manually enter the correct value in the Administrator password field after customization spec is deployed by thevRealize Suite Lifecycle Manager pipeline.
  • When a symptom definition is configured with REGEX or NOT_REGEX, the import fails when using the vRealize Operations Manager APIs with the following error. Error releasing Operations-Symptom message= "Invalid request... #1 violations found.","validationFailures":[{"failureMessage":"Message Event Condition field 'operator' must be either EQ or CONTAINS. If a symptom uses REGEX, the content must be imported manually by using vRealize Suite Lifecycle Manager.
  • A vRealize Suite Lifecycle Manager pipeline execution with a large number of captures or check-ins may fail if the number of executions is higher than those supported by the endpoint type.
  • When performing a multi-package capture, the entire capture fails with 409 conflict errors if there is a package with existing content.