Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
GH Issue: https://github.com/ManageIQ/manageiq-v2v/issues/731
GH PR: https://github.com/ManageIQ/manageiq-v2v/pull/732
New commit detected on ManageIQ/manageiq-v2v/master: https://github.com/ManageIQ/manageiq-v2v/commit/76dcd7fc0d1bb4117782cbc469d4fc145fb6e66b commit 76dcd7fc0d1bb4117782cbc469d4fc145fb6e66b Author: Mike Turley <mturley> AuthorDate: Wed Oct 24 10:31:11 2018 -0400 Commit: Mike Turley <mturley> CommitDate: Wed Oct 24 10:31:11 2018 -0400 Fix console error when editing a schedule less than 2 minutes in the future Fixes #731 https://bugzilla.redhat.com/show_bug.cgi?id=1642495 app/javascript/react/screens/App/Overview/components/ScheduleMigrationModal/ScheduleMigrationModalBody.js | 9 +- 1 file changed, 6 insertions(+), 3 deletions(-)
New commit detected on ManageIQ/manageiq-v2v/hammer: https://github.com/ManageIQ/manageiq-v2v/commit/5462e02859360c4545554b3e92cfea59d7b0fc3f commit 5462e02859360c4545554b3e92cfea59d7b0fc3f Author: Michael Ro <mikerodev> AuthorDate: Wed Oct 24 16:08:25 2018 -0400 Commit: Michael Ro <mikerodev> CommitDate: Wed Oct 24 16:08:25 2018 -0400 Merge pull request #732 from mturley/731-schedule-error [#731] Fix console error when editing a schedule less than 2 minutes in the future (cherry picked from commit 03793640000ed4f878bfc8291dbd591cecbc0907) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1642495 app/javascript/react/screens/App/Overview/components/ScheduleMigrationModal/ScheduleMigrationModalBody.js | 9 +- 1 file changed, 6 insertions(+), 3 deletions(-)
Tried mentioned steps and can't find console error when editing a schedule that is less than 2 minutes in the future. Verified on: 5.10.0.23.20181106165157_92dd189 Thank you!
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/RHSA-2019:0212