Deployment failed

This topic describes scenarios that can cause the deployment to fail. After the issue has been corrected, you must run the deployment again. If the deployment fails, check the error log in Infor CloudSuite Self-Service Portal for details.

Schema exists with the same name, but different type

If a schema with the same name but different object type already exists in the target tenant, the resource fails during the package deployment. All other resources in the global package will be deployed.

View references missing objects or properties in the target tenant

If a Data Lake view references an object or property that is not registered in the target tenant's Data Catalog, the resource fails during the package deployment. All other resources in the global package will be deployed.

Stream pipeline exists and is running in the target tenant

If one or more package stream pipelines already exist and are running in the target tenant, the import of those stream pipelines fails.

To resolve this issue, stop the existing stream pipelines in the target tenant and redeploy the package.

Stream pipeline exists in the target tenant with a different object name

If one or more package stream pipelines already exist in the target tenant but with different object names, those stream pipelines are deployed but their object names aren't updated. Object names can't be changed for stream pipelines that have been active at least once.

To resolve this issue, delete the existing stream pipelines in the target tenant and redeploy the package.

Security role already in use by another profile in the target tenant

If the security role that is associated with a profile in the global package already has a security profile in the target tenant, the security profile from the package is not imported and the deployment fails for that resource. Other resources without conflicts are deployed successfully.

To resolve the conflict, review the existing security profile in the target tenant and determine whether to retain it or replace it with the profile included in the package.

To use the security profile from the package, delete the existing profile from the target tenant, provided that the target tenant's profile is not a resource from another global package.

Caution: The deployment overwrites the security role's permissions with the permissions from the package.

After you resolve the conflict, redeploy the package.