Bug 1336184 - Smart State analysis task - spelling error
Summary: Smart State analysis task - spelling error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.6.0
Assignee: Mooli Tayer
QA Contact: Einat Pacifici
URL:
Whiteboard: container:smartstate
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-15 11:50 UTC by Einat Pacifici
Modified: 2018-04-02 12:58 UTC (History)
6 users (show)

Fixed In Version: 5.6.0.8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 16:02:38 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screen showing spelling mistake. (68.94 KB, image/png)
2016-05-15 11:50 UTC, Einat Pacifici
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description Einat Pacifici 2016-05-15 11:50:04 UTC
Created attachment 1157645 [details]
Screen showing spelling mistake.

Description of problem:
Run smart state analysis - see Tasks - spelling error: "Cannont analyze non docker images"

Version-Release number of selected component (if applicable):
5.6.0.6

How reproducible:
Always

Steps to Reproduce:
1.Run smart state analysis
2.Check Tasks list
3.When analysis fails error is displayed

Actual results:
Error wish spelling mistake is seen.
"Cannont analyze non docker images"

Expected results:
"Cannot analyze non docker images"

Additional info:
Screenshot attached.

Comment 2 Mooli Tayer 2016-05-16 21:39:19 UTC
proposed fix upstream:
https://github.com/ManageIQ/manageiq/pull/8749

Comment 4 errata-xmlrpc 2016-06-29 16:02:38 UTC
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-2016:1348


Note You need to log in before you can comment on or make changes to this bug.