Bug 1618804
| Summary: | [v2v] Schedule Unschedule Migration does not seem to work correctly | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Kedar Kulkarni <kkulkarn> | ||||||||||
| Component: | V2V | Assignee: | Michael Ro <micro> | ||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Kedar Kulkarni <kkulkarn> | ||||||||||
| Severity: | medium | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> | ||||||||||
| Priority: | high | ||||||||||||
| Version: | 5.9.4 | CC: | awight, bthurber, fdupont, hkataria, jprause, lavenel, mfeifer, mpovolny, obarenbo, simaishi, smallamp | ||||||||||
| Target Milestone: | GA | Keywords: | Regression, TestOnly, ZStream | ||||||||||
| Target Release: | 5.10.0 | Flags: | kkulkarn:
automate_bug+
|
||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | v2v | ||||||||||||
| Fixed In Version: | 5.10.0.21 | Doc Type: | If docs needed, set a value | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | |||||||||||||
| : | 1619654 (view as bug list) | Environment: | |||||||||||
| Last Closed: | 2019-02-12 16:49:32 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | V2V | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 1619654 | ||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 1476682 [details]
Screenshot
I also found 500 API error. See screenshot.
Please note, in some cases Unschedule button does show up correctly but throws Internal Server Error 500 as shown in attached screenshot. I believe thorough investigation of this feature is needed. Merged! On latest 5.10.0.14 build, Just before it starts running at scheduled time, "Unschedule" button changes to "Schedule" and then it starts running. So there is a brief window where : 1) User may think it is not scheduled any more. 2) User may try to Schedule it again. We should fix it. See attached Video. Created attachment 1481657 [details]
ScreenGIF2
Happening on Plans Completed Page.
Created attachment 1481658 [details]
ScreenGIF4
Happening on Plans Not started Page.
and merged! New commit detected on ManageIQ/manageiq-v2v/hammer: https://github.com/ManageIQ/manageiq-v2v/commit/43f99c2968faf92fbd0ee3afde8c50b6a72694e9 commit 43f99c2968faf92fbd0ee3afde8c50b6a72694e9 Author: Michael Ro <mikerodev> AuthorDate: Tue Oct 16 14:24:57 2018 -0400 Commit: Michael Ro <mikerodev> CommitDate: Tue Oct 16 14:24:57 2018 -0400 Merge pull request #711 from mturley/710-no-confusing-schedule-button [#710] Don't show Schedule button when scheduled migration is about to start (cherry picked from commit a561e5e20170af108c62e709e916d8917bd43d73) https://bugzilla.redhat.com/show_bug.cgi?id=1618804 app/javascript/react/screens/App/Overview/components/Migrations/MigrationsCompletedList.js | 20 +- app/javascript/react/screens/App/Overview/components/Migrations/MigrationsNotStartedList.js | 25 +- app/javascript/react/screens/App/Overview/components/Migrations/ScheduleMigrationButton.js | 14 +- app/javascript/react/screens/App/Overview/components/Migrations/helpers/getPlanScheduleInfo.js | 12 + 4 files changed, 50 insertions(+), 21 deletions(-) In 5.10.0.21 it does work correctly. |
Created attachment 1476647 [details] ScreenGIF1 Description of problem: Schedule Unschedule Migration does not seem to work correctly , see attached screenGIF Version-Release number of selected component (if applicable): 5.9.4.4 How reproducible: Believe 100% Steps to Reproduce: 1.See attached GIF 2. 3. Actual results: Unschedule does not seem to work well. Expected results: Once you schedule migration, button should change to Unschedule, and let you unschedule migration and after unscheduling, it should change to Schedule again. Additional info: