-
Bug
-
Resolution: Done-Errata
-
Blocker
-
MTC 1.8.4
-
None
-
None
-
False
-
-
False
-
ToDo
-
-
Description of problem:
When we perform a migration and it fails due to some reason, (either an existing DVM bug OR intentionally failing it by providing an invalid cluster_subdomain value inside the controller config) , the rollback of that migration also gets stuck at the quiescing step.
Version-Release number of selected component (if applicable):
MTC 1.8.4
How reproducible:
Always
Steps to Reproduce:
1.Deploy an application to migrate in the source cluster
2. Edit the migration controller configuration and set cluster_subdomain to abc.com
3. Execute cutover migration, and wait for the migration to fail.
4. Now perform rollback of the migration.
Actual results:
Rollback stuck at the quiescing step forever.
Expected results:
Rollback should complete successfully.
Additional info:
Migration contorller Logs keep printing
nd keeps printing this log {"level":"info","ts":1724167035.3108454,"logger":"migration","msg":"[RUN] (Step 8/15) Waiting for Quiesce (Scaling to 0 replicas) to finish for Deployments, DeploymentConfigs, StatefulSets, ReplicaSets, DaemonSets, CronJobs, Jobs and Virtual Machines in target namespace.","migMigration":"rollback-c3257","phase":"EnsureDestQuiesced"} {"level":"info","ts":1724167035.3115046,"logger":"migration","msg":"Found quiesced Pod on source cluster that has not yet terminated. Waiting.","migMigration":"rollback-c3257","phase":"EnsureDestQuiesced","pod":"django-tgt/django-psql-persistent-1-4254s","podPhase":"Running"} {"level":"info","ts":1724167035.3115325,"logger":"migration","msg":"Quiescing on source cluster is incomplete. Pods are not yet terminated, waiting.","migMigration":"rollback-c3257","phase":"EnsureDestQuiesced"}
- links to
-
RHSA-2024:130588
Migration Toolkit for Containers (MTC) 1.8.4 security and bug fix update
