Bug 177489 - Satellite Systems Properties can't be altered
Satellite Systems Properties can't be altered
Status: CLOSED CURRENTRELEASE
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server (Show other bugs)
400
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jesus M. Rodriguez
Red Hat Satellite QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-01-11 00:59 EST by Martin Zierer
Modified: 2008-03-13 22:19 EDT (History)
0 users

See Also:
Fixed In Version: sat510
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-13 22:19:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Martin Zierer 2006-01-11 00:59:15 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051202 Fedora/1.5-1.fc4.remi Firefox/1.5

Description of problem:
Within the Satellite web console under System -> Details -> Properties, if I try to change any field for any system that is managed by the Satellite server, I always get the following error message:

"A system name must contain only ascii characters."

At first, I thought it was one of my Solaris machines that I'm manaing with Satellite, but it's the same for all the RHEL machines.

I found the bug when I was trying to change the entitlements for the Solaris system.

Version-Release number of selected component (if applicable):
rhn-base-4.0.3-12.rhel3

How reproducible:
Always

Steps to Reproduce:
1. Log onto Satellite server web console
2. Go to "Systems" and choose one of the listed systems
3. Under "System properties" choose "Edit these properties"
4. Change any value and/or tick-box to produce the error message
  

Actual Results:  Error message "A system name must contain only ascii characters." appeared and record wasn't updated.

Expected Results:  Record should have been updated.

Additional info:
Comment 1 Jesus M. Rodriguez 2008-03-13 22:19:16 EDT
Fixed in the upcoming satellite 5.0 or greater

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