Bug 1429765

Summary: Deploymeant Typo on console page
Product: OpenShift Container Platform Reporter: Christian Marth <christian.marth>
Component: Management ConsoleAssignee: Jessica Forrester <jforrest>
Status: CLOSED ERRATA QA Contact: XiaochuanWang <xiaocwan>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: abhgupta, aos-bugs, jokerman, mmccomas, tdawson, wsun, yufchang
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-12 19:14:40 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:
Attachments:
Description Flags
Typo on console none

Description Christian Marth 2017-03-07 03:09:52 UTC
Created attachment 1260671 [details]
Typo on console

Description of problem: Typo on console page after creating a product


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


How reproducible:


Steps to Reproduce:
1. Login to openshift online
2. Create a new project
3. Observe console page

Actual results: Under Technologies There's a typo under Continous integration and deployment


Expected results: Deployment not Deploymeant


Additional info:

Comment 1 Jessica Forrester 2017-03-28 16:54:37 UTC
This was already fixed in 3.5

Comment 2 Jessica Forrester 2017-03-28 17:04:56 UTC
switching to modified so it can get into the errata

Comment 4 XiaochuanWang 2017-03-30 02:26:16 UTC
There is no 3.5 env for online, tested on OCP 3.5, version:
OpenShift Master:     v3.5.5
Kubernetes Master:    v1.5.2+43a9be4 
It's not reproduced on OCP 3.5

Comment 5 XiaochuanWang 2017-03-30 02:44:59 UTC
Since the bug is fixed on ocp 3.5, it could be Verified.

Comment 7 errata-xmlrpc 2017-04-12 19:14:40 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-2017:0884