GMU Error: Transaction rolled back because it has been marked as rollback-only

Products

• CA API Gateway

Issue/Introduction

When trying to migrateIn a bundle to a target Gateway after exporting all from a source Gateway, you receive the following error:

<l7:Error xmlns:l7="http://ns.l7tech.com/2010/04/gateway-management">
<l7:Type>UnexpectedRollback</l7:Type>
<l7:TimeStamp>2018-07-17T11:23:56.171-07:00</l7:TimeStamp>
<l7:Link rel="self" uri="https://<gateway_fqdn>:8443/restman/1.0/bundle?test=false&activate=true"/>
<l7:Detail>Transaction rolled back because it has been marked as rollback-only</l7:Detail>
</l7:Error>

Additionally, the following error messages (or similar) might be present in the ssg logs:

com.l7tech.external.assertions.apiportaldatalens.listener.ModuleListener: Could not save Api Portal Datasource Entity 'ssgDB'
com.l7tech.external.assertions.apiportaldatalens.listener.ModuleListener: Could not save Api Portal Datasource Entity 'LocalLoggerPOC'
com.l7tech.external.assertions.apiportaldatalens.listener.ModuleListener: Could not save Api Portal Datasource Entity 'Cache'
com.l7tech.external.assertions.apiportaldatalens.listener.ModuleListener: Could not save Api Portal Datasource Entity 'MigrationRouter'
com.l7tech.external.assertions.apiportaldatalens.listener.ModuleListener: Could not save Api Portal Datasource Entity 'portalDB'

Environment

Release:
Component: APIGTW

Resolution

Workaround:
 

Use the restman service to retireve the generic entity IDs and update the mapping file to Ignore them:

• Using a rest client (Postman, cURL, etc like GET https://fqdn:9443/restman/1.0/genericEntities/
• Find the IDs associated to the above from the output, and use GMU to set the action to ignore.
• Run the migrateIn command again.