Bug 1270610 - "Cannot Login. User Account has expired" because valid_from date is set in the future
Summary: "Cannot Login. User Account has expired" because valid_from date is set in th...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Setup.Engine
Version: 3.6.0.1
Hardware: All
OS: All
unspecified
urgent vote
Target Milestone: ovirt-3.6.0-ga
: 3.6.0
Assignee: Martin Perina
QA Contact: Ondra Machacek
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-11 20:32 UTC by Christopher Pereira
Modified: 2016-02-10 19:14 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-04 13:37:55 UTC
oVirt Team: Infra
rule-engine: ovirt-3.6.0+
ylavi: planning_ack+
oourfali: devel_ack+
pnovotny: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 46998 0 None None None Never
oVirt gerrit 47022 0 None None None Never

Description Christopher Pereira 2015-10-11 20:32:15 UTC
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.

Comment 1 Martin Perina 2015-10-14 06:10:00 UTC
Fix contained in ovirt-engine-extension-aaa-jdbc-1.0.0

Comment 2 Christopher Pereira 2015-10-14 10:47:25 UTC
(In reply to Martin Perina from comment #1)
> Fix contained in ovirt-engine-extension-aaa-jdbc-1.0.0

The bug was present in:
ovirt-engine-extension-aaa-jdbc-1.0.0-0.0.master.20150923074852.git46a67c9.el7.noarch

Installed via yum (3.6-rc1).

Comment 3 Martin Perina 2015-10-17 14:54:17 UTC
(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:
> ovirt-engine-extension-aaa-jdbc-1.0.0-0.0.master.20150923074852.git46a67c9.
> el7.noarch
> 
> 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

Comment 4 Ondra Machacek 2015-10-22 09:39:58 UTC
ovirt-engine-extension-aaa-jdbc-1.0.0-2.el6ev.noarch

[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';
         valid_from         
----------------------------
 2015-10-22 11:38:00.527+02
(1 row)

Comment 5 Sandro Bonazzola 2015-11-04 13:37:55 UTC
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.


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