Bug 1640279
Summary: | [RFE] A stray "0" character appears after the associated mapping name on a plan with no schedule | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Mike Turley <mturley> |
Component: | V2V | Assignee: | Brett Thurber <bthurber> |
Status: | CLOSED ERRATA | QA Contact: | Kedar Kulkarni <kkulkarn> |
Severity: | low | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
Priority: | medium | ||
Version: | 5.10.0 | CC: | fdupont, simaishi, smallamp |
Target Milestone: | GA | Keywords: | FutureFeature |
Target Release: | 5.10.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.10.0.21 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-02-07 23:03:44 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
Mike Turley
2018-10-17 18:27:46 UTC
New commit detected on ManageIQ/manageiq-v2v/hammer: https://github.com/ManageIQ/manageiq-v2v/commit/942454b933293c983c2876298d8421137a7bc918 commit 942454b933293c983c2876298d8421137a7bc918 Author: Michael Ro <mikerodev> AuthorDate: Thu Oct 18 13:21:05 2018 -0400 Commit: Michael Ro <mikerodev> CommitDate: Thu Oct 18 13:21:05 2018 -0400 Merge pull request #718 from mturley/stray-0-character-in-plans Prevent a stray 0 from appearing on plans with no schedule (cherry picked from commit 95650e6e8e4a5b925aaa4aa59433618b3c039712) https://bugzilla.redhat.com/show_bug.cgi?id=1640279 app/javascript/react/screens/App/Overview/components/Migrations/MigrationsCompletedList.js | 18 +- app/javascript/react/screens/App/Overview/components/Migrations/MigrationsNotStartedList.js | 17 +- 2 files changed, 16 insertions(+), 19 deletions(-) On 5.10.0.23 I do not see this issue. Fix Verified. 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 |