Red Hat Bugzilla – Bug 887744
Validation process for "current password" still display "Current Password Invalid" when force cursor on the current password field.
Last modified: 2014-01-21 14:17:35 EST
Description of problem: Validation process for "current password" still display "Current Password Invalid" when force cursor on the current password field and don't input anything. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.4-20121212.1.el6 How reproducible: 100% Steps to Reproduce: 1. Install RHEV-H first. 2. Boot from PXE choose the latest RHEV-H and press Enter key enter TUI upgrade process. 3. Force cursor on the current password field and don't input anything. Actual results: After step3,Validation process for "current password" still display "Current Password Invalid" Expected results: If force cursor on the current password field and don't input anything, the info "Current Password Invalid" shouldn't display below the input fields Additional info: ----------------
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Test version: rhev-hypervisor6-6.5-20131017.0.iso ovirt-node-3.0.1-4.el6 With new TUI, when force cursor on the current password field and don't input anything, the info "You have not provided a new password, current admin password will be used." display below the input fields so this bug has been fixed with new TUI redesign.
Thanks Haiyang.
Test version: rhevh-6.5-20131024.1.0.iso ovirt-node-3.0.1-6.el6.noarch.rpm With new TUI, when force cursor on the current password field and don't input anything, the info "You have not provided a new password, current admin password will be used." display below the input fields so this bug has been fixed with new TUI redesign.
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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. http://rhn.redhat.com/errata/RHBA-2014-0033.html