Bug 1326357 - Unable to create content host using any non Latin symbols
Summary: Unable to create content host using any non Latin symbols
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.2.0
Hardware: x86_64
OS: Linux
unspecified
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-12 14:00 UTC by Oleksandr Shtaier
Modified: 2016-04-12 17:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-12 17:28:13 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Oleksandr Shtaier 2016-04-12 14:00:33 UTC
Description of problem:
Trying to create new content host using utf-8 or Cyrillic symbols as a name:

>hammer -u user -p pass content-host create --content-view-id=1707 --lifecycle-environment-id=1640 --organization-id=1731 --name=укцкукцуцк
Could not create content host:
  ERROR:  null value in column "host_id" violates not-null constraint
  DETAIL:  Failing row contains (1297, null, 29, null, 2016-04-12 13:55:07.600381, 2016-04-12 13:55:07.600381).

>hammer -u admin -p changeme content-host create --content-view-id=1707 --lifecycle-environment-id=1640 --organization-id=1731 --name=鵾繉仿昛踃蔪斦鯟溨宦
Could not create content host:
  ERROR:  null value in column "host_id" violates not-null constraint
  DETAIL:  Failing row contains (1294, null, 29, null, 2016-04-12 13:50:56.297075, 2016-04-12 13:50:56.297075).

Version-Release number of selected component (if applicable):
6.2 SNAP 7.1

How reproducible:
Always

Steps to Reproduce:
Provided in description

Actual results:
Content host is not created and error is raised

Expected results:
Content host is created

Additional info:

Comment 3 Bryan Kearney 2016-04-12 17:28:13 UTC
Closing this out as WONTFIX. With host unification, the FQDN needs to be valid latin characters.


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