Bug 976761 - LocalizationService - Message with id: [systems.details.virt.actions.scheduled] not found.
Summary: LocalizationService - Message with id: [systems.details.virt.actions.schedule...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Provisioning
Version: 560
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks: sat560-lowbug
TreeView+ depends on / blocked
 
Reported: 2013-06-21 11:46 UTC by Lukas Pramuk
Modified: 2013-10-01 21:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-01 21:54:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukas Pramuk 2013-06-21 11:46:38 UTC
Description of problem:
Message "**systems.details.virt.actions.scheduled**" is displayed instead of some resonable text like e.g "Actions for virtual machines were successfully scheduled"

Version-Release number of selected component (if applicable):
Satellite-5.6.0-RHEL6-re20130607.1

How reproducible:
always

Steps to Reproduce:
0. have a VirtHost regged to Satellite and hosting at least 2 VMs (guests)
1. @webui: navigate to Systems - <chosen VHost> - Virtualization tab - Details subtab 
2. select at least two guests and Apply any action or Apply any changes (e.g. Restart systems)
3. confirmation pops up, click Confirm, et voila the message can be seen

Actual results:
displayed message contains placeholder "**systems.details.virt.actions.scheduled**"

Expected results:
displayed message contains reasonable text

Additional info:

Comment 1 Tomáš Kašpárek 2013-06-25 06:44:52 UTC
this issue is fixed in spacewalk.git by commit 13a5b7383b9c45865f917870ae33af4dc815cdce

Comment 4 Clifford Perry 2013-10-01 21:54:22 UTC
Satellite 5.6 has been released. This bug was tracked under the release.  

This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly
before release). 

Moving to CLOSED CURRENT_RELEASE. 

Text from Upgrade Erratum follows:

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.

http://rhn.redhat.com/errata/RHEA-2013-1395.html


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