Created attachment 1587194 [details] Disabled buttons Description of problem: Version-Release number of selected component (if applicable): 5.10.6.1.20190621202107_58f5bbc How reproducible: Steps to Reproduce: 1. Create migration map 2. create migration plan using map created on step 1 3. On final stage of migration plan creation, "Cancel" and "Back" are disabled. Actual results: Expected results: Additional info:
@Vince, do you think it should be fixed or is it the intended behavior ?
@Fabien This should be fixed. We're tracking it here: https://github.com/ManageIQ/manageiq-v2v/issues/1000
New commit detected on ManageIQ/manageiq-v2v/ivanchuk: https://github.com/ManageIQ/manageiq-v2v/commit/17128358c059632dc41a46f356f1a104a9d9ae5b commit 17128358c059632dc41a46f356f1a104a9d9ae5b Author: Milan Zázrivec <mzazrivec> AuthorDate: Thu Jul 25 07:49:59 2019 -0400 Commit: Milan Zázrivec <mzazrivec> CommitDate: Thu Jul 25 07:49:59 2019 -0400 Merge pull request #1009 from mturley/1000-hide-back-cancel-on-end-of-wizards Hide Back and Cancel buttons on the last step of Migration wizards (cherry picked from commit 145211cda87a3fa5b5c4459b7f81d68eaf48fb32) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1726844 app/javascript/react/screens/App/Mappings/screens/MappingWizard/MappingWizard.js | 36 +- app/javascript/react/screens/App/Mappings/screens/MappingWizard/__tests__/__snapshots__/MappingWizard.test.js.snap | 56 +- app/javascript/react/screens/App/Overview/screens/PlanWizard/PlanWizard.js | 18 +- app/javascript/react/screens/App/Settings/screens/ConversionHostsSettings/components/ConversionHostWizard/ConversionHostWizard.js | 23 +- app/javascript/react/screens/App/Settings/screens/ConversionHostsSettings/components/ConversionHostWizard/__tests__/__snapshots__/ConversionHostWizard.test.js.snap | 52 +- 5 files changed, 92 insertions(+), 93 deletions(-)
Created attachment 1599245 [details] Buttons removed
Verified in 5.11.0.17.20190730152352_93b1c30
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, 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-2019:4199