Bug 155055 - Installer does not handle certain characters correctly (e.g. '=')
Installer does not handle certain characters correctly (e.g. '=')
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Installer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Robin Norwood
Max Spevack
Depends On:
Blocks: 147875
  Show dependency treegraph
Reported: 2005-04-15 17:06 EDT by Taco Scargo
Modified: 2007-08-06 12:09 EDT (History)
1 user (show)

See Also:
Fixed In Version: RHN 4.0.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-31 22:22:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Taco Scargo 2005-04-15 17:06:18 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; chrome://navigator/locale/navigator.properties; rv:1.7.5) Gecko/20041107 Firefox/1.0

Description of problem:
While installing Satellite 3.7 and entering the username/password for oracle, the application did not accept the entries (resetting them to the defaults and not continuing). Found out that it did not like the '=' sign in the password. Apparently the regex scripting to enter the values in the rhn config file is not correct and does not 'escape' the strings entered. After changing the oracle password everything worked fine. No error message was displayed.

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

How reproducible:

Steps to Reproduce:
1. Setup an oracle sid, user and password with a password containing the = character
2. install satellite
3. try to complete the web-wizard

Actual Results:  It is stuck on the page where you have to enter the oracle details

Expected Results:  Accept entries and continue

Additional info:
Comment 2 Robin Norwood 2005-06-15 11:47:34 EDT
Fixed in CVS - 

Test plan:

1) Set up an external DB with a password that contains the '=' character.
  - Someone smart (like jslagle, for instance...) can help you set this up.
2) Install a satellite using that database. (ie, use the non-embedded iso)
3) At the db_config.pxt, enter the db information, and click 'submit'.
  - Expect to continue to the DB population phase.
4) Complete the DB population.  At this point you can be relatively sure the bug
is fixed.
Comment 3 Max Spevack 2005-07-13 14:14:16 EDT
I followed the testplan with a password containing an = and everything was fine.

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