Bug 1482464 - Wrong word 'succesfully' in prompt message
Summary: Wrong word 'succesfully' in prompt message
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 3.7.0
Assignee: Samuel Padgett
QA Contact: XiaochuanWang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-17 10:51 UTC by Yadan Pei
Modified: 2017-11-28 22:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-11-28 22:07:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 0 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-29 02:34:54 UTC

Description Yadan Pei 2017-08-17 10:51:23 UTC
Description of problem:
Incorrect word 'succesfully' in message when adding config files to dc

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

How reproducible:
Always

Steps to Reproduce:
1.Create DC
oc run myrun --image=aosqe/hello-openshift
2.Go to DC -> Configuration tab -> Click "Add Config Files" -> select one secret -> add Mount Path: /datasecret -> Click Add

Actual results:
2. After changes is added, message prompted: Succesfully added secret builder-dockercfg-lth9q to deployment config myrun

Expected results:
2. It should be 'Successfully'

Additional info:

Comment 3 Yadan Pei 2017-10-09 07:10:02 UTC
Checked on v3.7.0-0.143.1, the issue has been fixed

Move to VERIFIED

Comment 6 errata-xmlrpc 2017-11-28 22:07:08 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/RHSA-2017:3188


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