Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1482464 - Wrong word 'succesfully' in prompt message
Wrong word 'succesfully' in prompt message
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console (Show other bugs)
3.6.0
Unspecified Unspecified
medium Severity low
: ---
: 3.7.0
Assigned To: Samuel Padgett
XiaochuanWang
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-17 06:51 EDT by Yadan Pei
Modified: 2017-11-28 17:07 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-28 17:07:08 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-28 21:34:54 EST

  None (edit)
Description Yadan Pei 2017-08-17 06:51:23 EDT
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 03:10:02 EDT
Checked on v3.7.0-0.143.1, the issue has been fixed

Move to VERIFIED
Comment 6 errata-xmlrpc 2017-11-28 17:07:08 EST
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.