Bug 1916554
| Summary: | Direct Volume Migration pods stuck at ContainerCreating status when PVC is in 'Terminating' state | ||
|---|---|---|---|
| Product: | Migration Toolkit for Containers | Reporter: | Xin jiang <xjiang> |
| Component: | General | Assignee: | Jaydip Gabani <jgabani> |
| Status: | CLOSED ERRATA | QA Contact: | Xin jiang <xjiang> |
| Severity: | medium | Docs Contact: | Avital Pinnick <apinnick> |
| Priority: | medium | ||
| Version: | 1.4.0 | CC: | chezhang, ernelson, rjohnson, sregidor, whu |
| Target Milestone: | --- | ||
| Target Release: | 1.4.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-03-15 08:15:36 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Xin jiang
2021-01-15 03:27:33 UTC
This is something we'd like to fix but not something I'd consider to be critically severe. in MTC 3.11(controller)-> 4.7, it has different behavior. Not sure if they are same reason that Unable to mount volumes for pod.
1. I didn't see DVM pod was started creating.
$ oc get migmigration 3db53140-6143-11eb-8e38-431dc1d3e8a0 -o yaml
....
status:
conditions:
- category: Advisory
lastTransitionTime: "2021-01-28T08:32:41Z"
message: 'Step: 36/47'
reason: WaitForDirectVolumeMigrationToComplete
status: "True"
type: Running
- category: Required
lastTransitionTime: "2021-01-28T08:31:39Z"
message: The migration is ready.
status: "True"
type: Ready
itinerary: Final
observedDigest: f19ac39779c0d0ee1443c3580dad86e38eafa02a1cb4bdff18cac9c14b520005
phase: WaitForDirectVolumeMigrationToComplete
pipeline:
- completed: "2021-01-28T08:32:08Z"
message: Completed
name: Prepare
started: "2021-01-28T08:31:39Z"
- completed: "2021-01-28T08:32:33Z"
message: Completed
name: Backup
progress:
- 'Backup openshift-migration/3db53140-6143-11eb-8e38-431dc1d3e8a0-ddxlj: 76 out of estimated total of 76 objects backed up (15s)'
started: "2021-01-28T08:32:08Z"
- completed: "2021-01-28T08:32:39Z"
message: Completed
name: StageBackup
started: "2021-01-28T08:32:33Z"
- message: Skipped
name: StageRestore
skipped: true
- completed: "2021-01-28T08:32:41Z"
message: Waiting for Direct Image Migration to complete.
name: DirectImage
phase: WaitForDirectImageMigrationToComplete
progress:
- 1 total ImageStreams; 0 running; 1 successful; 0 failed
- 'ImageStream ocp-django/django-psql-persistent (dism openshift-migration/3db53140-6143-11eb-8e38-431dc1d3e8a0-6v5nt-k8ngv): Completed '
started: "2021-01-28T08:32:39Z"
- name: DirectVolume
phase: WaitForDirectVolumeMigrationToComplete
progress:
- 1 total volumes; 0 successful; 0 running; 0 failed
started: "2021-01-28T08:32:41Z"
- message: Not started
name: Restore
- message: Not started
name: Cleanup
startTimestamp: "2021-01-28T08:31:39Z"
$ oc get event -n ocp-django
......
1h 1h 1 django-psql-persistent-1-deploy.165e562824ce6e67 Pod spec.containers{deployment} Normal Killing kubelet, ip-172-18-7-104.ec2.internal Killing container with id docker://deployment:Need to kill Pod
45m 45m 1 postgresql.165e584151ad2755 DeploymentConfig Normal ReplicationControllerScaled deploymentconfig-controller Scaled replication controller "postgresql-1" from 1 to 0
45m 45m 1 django-psql-persistent-1-vbdtm.165e58417b74be00 Pod spec.containers{django-psql-persistent} Normal Killing kubelet, ip-172-18-13-30.ec2.internal Killing container with id docker://django-psql-persistent:Need to kill Pod
45m 45m 1 postgresql-1.165e58415a03fdc9 ReplicationController Normal SuccessfulDelete replication-controller Deleted pod: postgresql-1-j5kwc
45m 45m 1 django-psql-persistent-1.165e5841538da3c3 ReplicationController Normal SuccessfulDelete replication-controller Deleted pod: django-psql-persistent-1-vbdtm
45m 45m 1 django-psql-persistent.165e58414fdba442 DeploymentConfig Normal ReplicationControllerScaled deploymentconfig-controller Scaled replication controller "django-psql-persistent-1" from 1 to 0
45m 45m 1 postgresql-1-j5kwc.165e58416275175a Pod spec.containers{postgresql} Normal Killing kubelet, ip-172-18-9-34.ec2.internal Killing container with id docker://postgresql:Need to kill Pod
https://github.com/konveyor/mig-controller/pull/958 the cp PR to bring change in the release branch is: https://github.com/konveyor/mig-controller/pull/972 verified. talked with Jaydip, it just shows up a warning on UI as below. The whole migration still is stuck there as if problem is fixed, the migration can continue the rest phases, it won't wast time. Warning alert:Paused - waiting for route to be admitted Pods directvolumemigration-rsync-transfer-mysql/ocp-24769-cakephp are stuck in Pending state for more than 10 mins Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Migration Toolkit for Containers (MTC) image release advisory 1.4.2), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:0814 |