During migration the server running in the migration pod can be started multiple time. Each time it attempts to configure the server.
It was not an issue when sed was used to configure the server, now that we are using CLI, CLI script can't be run multiple time.
So the migration pod server must be configured once before entering the migration loop.
- is blocked by
-
JBEAP-18533 Migration pod fails to start due to clustering.jgroups.channel.ee: java.lang.IllegalStateException
- Closed
- is caused by
-
JBEAP-18395 openshift-migrate.sh script fails on eap73-openjdk8-openshift-rhel7 due to missing /opt/eap/bin/launch/configure.sh
- Closed
- is cloned by
-
CLOUD-3471 Can't run multiple server during migration
- New
- is related to
-
CLOUD-3520 Can't configure multiple server during migration
- Closed