Cannot create loans due to incorrect meeting start date for some centers

Description

Using a July 31, 2008 backup of data from their v1.0 production system, GK
upgraded the DB and found that loan accounts could not be created for clients in
some centers. Upon looking into the issue further, they found that the meeting
start dates in the 'meeting' table had been altered after upgrade for these
centers to a date in the future (rather than remaining in the past) and so loan
accounts could not be created because the disbursal dates were prior to the
meeting start date for these centers.

We do not have the July 31 backup from GK to confirm this behavior on the
centers where they are seeing the issue.

I suspect this issue is due to meeting days being changed and the batch job not
updating the meeting start date correctly. There are two approaches to research
this issue until we get more clarity from GK on the issue:

1. Take our May snapshot of the GK db, upgrade it, run batch jobs and then
compare the start dates in the meeting table for the pre and post-upgrade DBs to
see if they are different.

2. Take a v1.0 DB with a center created in the past, upgrade DB to v1.1, change
the meeting day for the center and see if the meeting start date is updated
correctly or incorrectly.

Attached is the email provided by Naganand describing the problem. I'll update
this issue when I have more information from the above research and from talking
to Naganand further.

Environment

Platform: All, OS: All

Activity

Show:
Kay Chau
August 27, 2008, 6:54 PM

Reassign to Aliya for more info

aliyaw
August 28, 2008, 9:32 PM

Changing the "Found-in" version to v1.0. It turns out that I was mistaken about
this issue. It is happening in v1.0 in production and is not related to the
v1.1 upgrade. Basically, something is causing the values for the meeting start
date in the meeting table to change in production to dates in the future, which
prevents new loans from being created for that center before the value of the
meeting start date in the meeting table.

This issue started happening recently and wasn't observed before. We are going
to upgrade GK to v1.1 and monitor whether this continues to happen. We will
probably have to determine what is causing it from investigating the code since
we cannot figure out a clear repro to make this happen from the UI. This is
potentially caused by some issue in the batch jobs.

In the mean time, GK is manually changing the value of the meeting start date
back to the Center creation date (which is a date in the past).

Kay Chau
September 3, 2008, 6:08 PM

move to vRhino Backlog

aliyaw
November 4, 2008, 7:59 PM

Assigning this issue to Emily to follow up on research for GK

emilytucker
January 22, 2010, 9:21 PM

Assuming that this is no longer happening for GK-- so marking it as resolved.

Cannot Reproduce

Assignee

emilytucker

Reporter

aliyaw

Labels

URL

None

Story Points

None

Team

None

Scheduled For

None

Epic

None

Notify

None

productboard URL

None

Man Day Estimate

None

Components

Affects versions

Priority

Critical
Configure