Bug 1199794

Summary: [ALL_LANG] Incompleted message "Successfully deleted ." with a missing variable
Product: Red Hat Satellite Reporter: Yuko Katabami <ykatabam>
Component: Localization and InternationalizationAssignee: Dominic Cleal <dcleal>
Status: CLOSED CURRENTRELEASE QA Contact: Omri Hochman <ohochman>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: asasaki, bkearney, cwelton, mburns, mmccune, rhos-maint, tchuang, yeylon
Target Milestone: UnspecifiedKeywords: Triaged, ZStream
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 15:20:09 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
successfully-deleted in ja-JP none

Description Yuko Katabami 2015-03-08 12:11:00 UTC
Created attachment 999317 [details]
successfully-deleted in ja-JP

Description of problem:
"Successfully deleted ." message is missing the object.
As result, both English and localized strings appear incomplete.

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


How reproducible: 100%


Steps to Reproduce:
1. Log in to the installer.
2. Click OpenStack Installer -> Deployments
3. Click "Delete" button for a deployment and confirm the action.
4. Check the message shown on the top right.

Actual results:
English: Successfully deleted .
Japanese: が正常に削除されました。


Expected results:
English: Successfully deleted a deployment.
Japanese: デプロイメントが正常に削除されました。

Additional info:

Comment 5 Mike Burns 2015-03-11 16:26:14 UTC
This field is in core foreman, moving to that component.

Comment 8 RHEL Program Management 2015-04-30 16:03:49 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 13 Bryan Kearney 2015-08-12 15:20:09 UTC
This fix was delivered with Satellite 6.1.1 which was delivered on 12 August, 2015.