GMU Migrations Failing After Update

Products

• CA API Gateway

Issue/Introduction

After upgrading a lower environment, I am unable to migrate using GMU due to a conflict. This is across pretty much all APIs. 

Error results file

<l7:Mapping action="NewOrExisting" errorType="UniqueKeyConflict" srcId="69c60df0e823fc3239f2c81f245e8df7" srcUri="https://<gateway_hostname>:8443/restman/1.0/serverModuleFiles/69c60df0e823fc3239f2c81f245e8df7" type="SERVER_MODULE_FILE">

                <l7:Properties>

                    <l7:Property key="ErrorMessage">

                        <l7:StringValue>Other entity exists with the given id: 69c60df0e823fc3239f2c81f245e8df7</l7:StringValue>

                    </l7:Property>

                    <l7:Property key="MapBy">

                        <l7:StringValue>moduleSha256</l7:StringValue>

                    </l7:Property>

                </l7:Properties>

Cause

The SERVER_MODULE_FILE between the source and destination are different.

Resolution

If they are to remain that way, you can ignore the SERVER_MODULE using manageMapping as followed 

GMU.BAT manageMappings --type SERVER_MODULE_FILE --action ignore --bundle migration.xml

Running....

Updated mappings value:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<l7:Mapping xmlns:l7="http://ns.l7tech.com/2010/04/gateway-management" action="Ignore" srcId="69c60df0e823fc3239f2c81f245e8df7" srcUri="https://<gateway_hostname>:8443/restman/1.0/serverModuleFiles/69c60df0e823fc3239f2c81f245e8df7" type="SERVER_MODULE_FILE">

    <l7:Properties>

        <l7:Property key="MapBy">

            <l7:StringValue>moduleSha256</l7:StringValue>

        </l7:Property>

    </l7:Properties>

</l7:Mapping>