Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 979350

Summary: Changes admin password in the first time when log in is failed while finished auto-install
Product: [Retired] oVirt Reporter: wanghui <huiwa>
Component: ovirt-nodeAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: cshao, dougsland, fdeutsch, gouyang, hadong, jboggs, leiwang, mgoldboi, ovirt-maint, rbalakri, ycui
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: node
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-17 12:24:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description wanghui 2013-06-28 09:48:26 UTC
Description of problem:
After auto-install, it will request you to change the admin password in the first time when you log in. But it reports that authentication token manipulation error after you set the password in valid password.

Version-Release number of selected component (if applicable):
ovirt-node-iso-3.0.0-0.999.999.20130627023857git54b48f3.2632.fc18.iso
ovirt-node-3.0.0-1.0.fc18.noarch

How reproducible:
100%

Steps to Reproduce:
1. Clean auto-install ovirt-node-iso-3.0.0-0.999.999.20130627023857git54b48f3.2632.fc18.iso with adminpw.  
2. Log in ovirt-node using admin.
3. Change the password with valid format as requested.

Actual results:
After step3, it reports that authentication token manipulation error after you set the password in valid password.

Expected results:
After step3, it can set the password as you set and log in successfully.

Additional info:

Comment 1 Sandro Bonazzola 2014-10-17 12:24:34 UTC
oVirt 3.5 has been released and should include the fix for this issue.