Content Issues You might Encounter

There can be content issues that you might encounter during any content operations.

• 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 the Lifecycle Manager pipeline.
• When a symptom definition is setup with REGEX or NOT_REGEX, the import fails 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 needs to be imported manually through Lifecycle Manager UI.
• Content release from different versions of vRealize Operations Manager may fail. For example, content from 6.6 to 6.7 some content types may fail.
• A pipeline execution with a large number of captures or check-ins may fail, if the number of executions is higher than that supported by the endpoint type. For example, bitbucket cloud can support 1000 accesses per hour to its respository.