AnsweredAssumed Answered

Execution failed. Reason: Migrate in failed: Conflict

Question asked by MarijaOmniSecure on May 11, 2018
Latest reply on May 15, 2018 by wauch01

When running the comand:

$ ./GatewayMigrationUtility.sh migrateIn -z argFile/gateway2.arg -b all_2.xml --trustCertificate

i get an error like this:

Execution failed. Reason: Migrate in failed: Conflict

 

Thus is what the gmu.log file says:

 

May 11, 2018 11:22:35 AM com.ca.gateway.rest.commandline.command.GatewayCommand setClientConfig
WARNING: TLS hostname verification has been disabled
May 11, 2018 11:22:35 AM com.ca.gateway.rest.commandline.command.GatewayCommand setClientConfig
WARNING: TLS server certificate check has been disabled
May 11, 2018 11:22:35 AM com.ca.gateway.rest.commandline.command.Command runCommand
INFO: Running Command: migrateIn
May 11, 2018 11:24:05 AM com.ca.gateway.rest.commandline.command.MigrateInCommand run
WARNING: Migrate in failed: Conflict
May 11, 2018 11:24:06 AM com.ca.gateway.rest.commandline.command.Command runCommand
WARNING: Error executing command
java.lang.IllegalArgumentException: Migrate in failed: Conflict
    at com.ca.gateway.rest.commandline.command.MigrateInCommand.run(Unknown Source)
    at com.ca.gateway.rest.commandline.command.GatewayCommand.run(Unknown Source)
    at com.ca.gateway.rest.commandline.command.Command.runCommand(Unknown Source)
    at com.ca.gateway.rest.commandline.Main.main(Unknown Source)

 

Any ideas?

Outcomes