Bug 1837656
| Summary: | MigPlan is showing Migration Succeeded status on UI when the migration failed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Erik Nelson <ernelson> | ||||
| Component: | Migration Tooling | Assignee: | John Matthews <jmatthew> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Xin jiang <xjiang> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.4 | CC: | chezhang, ernelson, ibolton, jmatthew, mberube, rjohnson, sregidor, whu, xjiang | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.4.z | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 1837468 | Environment: | |||||
| Last Closed: | 2020-09-15 21:40:49 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1837468 | ||||||
| Bug Blocks: | |||||||
| Attachments: | 
            
  | 
      ||||||
| 
 
        
          Description
        
        
          Erik Nelson
        
        
        
        
        
          2020-05-19 18:45:56 UTC
        
       
      
      
      
    Engineering test with latest 1.2 images and wasn't able to reproduce, think this got fixed in a prior release. it occured once yesterday, please see the screenthos. I was using the latest image. Created attachment 1702790 [details]
cam1.2.4_screenshot
    It's not easy to reproduce it, maybe it depend on the phase where we canceled it. I will try to give you detailed step to reproduce it if I can. Closing this as a dup so we just focus on the fix aligned to 1.3.0 (in BZ 1837468) as we don't plan for future 1.2.z at this point. *** This bug has been marked as a duplicate of bug 1837468 ***  |