Red Hat Bugzilla – Bug 1270610
"Cannot Login. User Account has expired" because valid_from date is set in the future
Last modified: 2016-02-10 14:14:33 EST
Probably because of timezone configuration, engine-setup created/updated users table with new field "valid_from" set to "2015-10-11 20:13:45.408-04" (on "aaa_jdbc" schema).
But current date is "Sun Oct 11 17:25:57 CLT 2015" so user cannot login.
I workarrounded by changing valid_from date:
SET search_path TO aaa_jdbc;
update users set valid_from = '2001-01-01';
Please note there are other BZ reports suffering from the same issue and people probably will get confused trying to replicate/debug the problem because it fixes automatically when valid_from gets valid some time later.
Fix contained in ovirt-engine-extension-aaa-jdbc-1.0.0
(In reply to Martin Perina from comment #1)
> Fix contained in ovirt-engine-extension-aaa-jdbc-1.0.0
The bug was present in:
Installed via yum (3.6-rc1).
(In reply to Christopher Pereira from comment #2)
> (In reply to Martin Perina from comment #1)
> > Fix contained in ovirt-engine-extension-aaa-jdbc-1.0.0
> The bug was present in:
> Installed via yum (3.6-rc1).
I meant ovirt-engine-extension-aaa-jdbc-1.0.0-2, the above was just snapshot build.
Anyway this is fixed in oVirt 3.6.0 RC2
[root@om-ovirt36 ~]# date
Thu Oct 22 11:37:51 CEST 2015
[root@om-ovirt36 ~]# ovirt-aaa-jdbc-tool user add userX
adding user userX...
user added successfully
engine=# select valid_from from aaa_jdbc.users where name = 'userX';
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.