Description of problem: When using the redhat_register snipped in the default RHEL kickstart, the use of double quotes for the password entry can cause evaluation problems when a special character is in use in the password. As the password is not evaluated properly an 'Invalid Username/Password' error is displayed. This has more serious consequences as the machine proceeds to reboot after a failed registration, updates are not applied, puppet is not installed, and the OpenStack packages are not installed/configured as required. When the kickstart is manually edited to use single quotes, it allows both normal passwords and passwords with special characters to go through successfully. Suggest we implement a patch to set this or at the very least document this requirement. Version-Release number of selected component (if applicable): RHEL OSP 5.0 on RHEL 7.0 RHEL OSP Installer (Staypuft) GA3 (pre-A1) How reproducible: Every time. Steps to Reproduce: 1. Install RHEL OSP Installer and set subscription manager details, using your password that contains special characters 2. Create an OpenStack deployment 3. Deploy your OpenStack environment and watch logs Actual results: Invalid Username/Password error message displayed, box reboots with no services installed, puppet included (as it's shipped in rhelosp5 channel). Expected results: Username/password parsed properly, system registered and required components installed. Additional info: As above, setting the kickstart to use single quotes gets around this problem and allows passwords containing special characters to go through too.
https://github.com/theforeman/foreman-installer-staypuft/pull/99
Verified: rhel-osp-installer-0.3.6-1.el6ost.noarch openstack-foreman-installer-2.0.26-1.el6ost.noarch openstack-puppet-modules-2014.1-21.8.el6ost.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noar Successfully registered a machine to cdn using a password with special chars and bearing in mind BZ #1070388
doc text looks correct to me, removing needinfo
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. https://rhn.redhat.com/errata/RHBA-2014-1800.html