Bug 1168647 - Error creating Sync Plans with Russian locale
Summary: Error creating Sync Plans with Russian locale
Keywords:
Status: CLOSED DUPLICATE of bug 1140507
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.4
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-27 13:44 UTC by Dmitry Patrakov
Modified: 2017-02-23 20:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-28 08:31:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
archive contains the screenshots (62.76 KB, application/x-gzip)
2014-11-27 13:44 UTC, Dmitry Patrakov 		no flags Details
View All

Description Dmitry Patrakov 2014-11-27 13:44:44 UTC 
Created attachment 962019 [details]
archive contains the screenshots

Description of problem:
Error creating Sync Plans with Russian locale

Version-Release number of selected component (if applicable):
RHEL 6.6 x86_64
RH Satellite 6.0.4

How reproducible:
always

Steps to Reproduce:
1. I set the following settings in "Admin user"->"My account":
Language = Browser Locale (I have a Russian locale)
2. I tried to create a "Sync Plans"
3. When I choose a "daily" interval (russian: "ежедневно"), I got a error: "имеет непредусмотренное значение", means that "error value". 

When I switch interface to English - everything worked fine.

Actual results:
error: "имеет непредусмотренное значение"

Expected results:


Additional info:
Comment 1 RHEL Program Management 2014-11-27 13:53:45 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 3 Dominic Cleal 2014-11-28 08:31:52 UTC 
This was fixed in the following erratum: https://access.redhat.com/errata/RHBA-2014:1857

*** This bug has been marked as a duplicate of bug 1140507 ***
Note You need to log in before you can comment on or make changes to this bug.