Re: Fineract 1.5.0 to 1.6.0 upgrade

[Kelvin Ikome]

Hi all,

I did not run into any further liquibase issues on merging from the 1.6
tag.

The issues I ran into were only in cases where trying to run with existing
1.5 DB, some migration scripts did not run which led to some operations
failing due to slight differences in schema. I resolved this by running the
missing migrations manually.

Kind regards,
Kelvin

On Fri, Apr 22, 2022 at 11:39 AM Manoj VM  wrote:

> ... we have used this commit hash
>  746c589a6e809b33d68c0596930fcaa7338d5270
> and flywy migration is done to the latest.
>
> TENANT_LATEST_FLYWAY_VERSION = 392;
> TENANT_LATEST_FLYWAY_SCRIPT_NAME =
> "V392__interest_recovery_conf_for_rescedule.sql";
> TENANT_LATEST_FLYWAY_SCRIPT_CHECKSUM = 1102395052;
>
>
>
> On Fri, 22 Apr, 2022, 12:17 Arnold Galovics, 
> wrote:
>
>> Hey guys,
>>
>> I'm not really sure what happened, maybe we mistagged the release by a
>> single commit because the original idea was definitely that the 1.6 release
>> will be the latest one doing the database migrations using Flyway.
>>
>> Could we retag the previous commit (what Manoj used) with 1.6 and drop
>> the current one? What are the implications there?
>>
>> Best,
>> Arnold
>>
>> On Thu, Apr 21, 2022 at 7:58 PM James Dailey 
>> wrote:
>>
>>> Manoj
>>>
>>> Thanks for digging into that.
>>>
>>> Yes, the TenantDatabaseUpgradeService.java file is in the release
>>> source code Zip file with the liquibase migration on Upgrade.
>>>
>>> @Aleksandar Vidakovic   I think we want to
>>> be even more clear about the migration path.
>>>
>>> I believe that release 1.6 was aiming to be the last version that used
>>> Flyway to upgrade to the 1.6 version.  ??
>>> Thereafter, the requirement would be to drop Flyway and use Liquibase
>>> for both migrations and database independence.
>>>
>>>  applyInitialLiquidbase() is something to be triggered once running on
>>> 1.6?
>>>
>>> I'm probably not following the logic well enough.  So, please correct
>>> me.
>>>
>>>
>>>
>>> On Thu, Apr 21, 2022 at 9:54 AM Manoj VM  wrote:
>>>
 ...  I have done the troubleshooting and found that the Liquibase
 changes are part of 1.6 tag.

 Ref
 https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java


 We have taken a workaround to do migration to commit prior to this
 change first, and then migrate to 1.6.  it is a long short.  Any other
 suggestions are welcome.

 Thanks,
 Manoj

 On Thu, 21 Apr, 2022, 03:49 Aleksandar Vidakovic, <
 chee...@monkeysintown.com> wrote:

> so, are you dropping the schema_version table yourself or is Liquibase
> doing that? Latter would be kind of plausible, because why keep it if
> there's no more Flyway; and overall this shouldn't influence anything
> here... the migration failures are a bit of a surprise here though (this
> was tested quite extensively) could you send stacktraces or similar to
> get an idea where exactly things seem to break on your end? I suspect
> there's something else going on... unless we have more people with similar
> issues? But again, the first time I've heard it now... maybe we can sort 
> it
> out here... if it's affecting a broader audience then we have to crank out
> a patch release with a fix.
>
> ... if you could send the errors here then we can see how we can get
> this fixed for you or find any other workaround.
>
> Cheers,
>
> Aleks
>
> On Wed, Apr 20, 2022 at 6:24 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> ... first time I heard it... Kelvin: are we sure that there was no
>> quick pull from the develop branch and that got started at one point? I
>> know that this kind of "upgrade" is quite popular, but this doesn't 
>> really
>> fly anymore with the mechanics in place.
>>
>> On Wed, Apr 20, 2022 at 5:02 PM Arnold Galovics <
>> galovicsarn...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> It's strange because the 1.6 version shouldn't include Liquibase. We
>>> only wanted to release it after 1.6.
>>>
>>> @Aleks, did we mix it up somehow?
>>>
>>> Best,
>>> Arnold
>>>
>>> On Tue, Apr 19, 2022 at 4:59 PM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 @Arnold could you chime in here and help Manoj?

 On Tue, Apr 19, 2022 at 12:38 PM Manoj VM 
 wrote:

> Hi Aleksandar Vidakovic,
>
> Is there any update that happened to the 1.6 release?
>
> We are getting *"SchemaUpgradeNeededException: Make sure to
> upgrade to Fineract 1.6 first and then to a newer version"* error
> while upgrading to *tag 1.6*
>
> ref:
> https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Manoj VM]

... we have used this commit hash
 746c589a6e809b33d68c0596930fcaa7338d5270
and flywy migration is done to the latest.

TENANT_LATEST_FLYWAY_VERSION = 392;
TENANT_LATEST_FLYWAY_SCRIPT_NAME =
"V392__interest_recovery_conf_for_rescedule.sql";
TENANT_LATEST_FLYWAY_SCRIPT_CHECKSUM = 1102395052;



On Fri, 22 Apr, 2022, 12:17 Arnold Galovics, 
wrote:

> Hey guys,
>
> I'm not really sure what happened, maybe we mistagged the release by a
> single commit because the original idea was definitely that the 1.6 release
> will be the latest one doing the database migrations using Flyway.
>
> Could we retag the previous commit (what Manoj used) with 1.6 and drop the
> current one? What are the implications there?
>
> Best,
> Arnold
>
> On Thu, Apr 21, 2022 at 7:58 PM James Dailey 
> wrote:
>
>> Manoj
>>
>> Thanks for digging into that.
>>
>> Yes, the TenantDatabaseUpgradeService.java file is in the release
>> source code Zip file with the liquibase migration on Upgrade.
>>
>> @Aleksandar Vidakovic   I think we want to be
>> even more clear about the migration path.
>>
>> I believe that release 1.6 was aiming to be the last version that used
>> Flyway to upgrade to the 1.6 version.  ??
>> Thereafter, the requirement would be to drop Flyway and use Liquibase for
>> both migrations and database independence.
>>
>>  applyInitialLiquidbase() is something to be triggered once running on
>> 1.6?
>>
>> I'm probably not following the logic well enough.  So, please correct me.
>>
>>
>>
>>
>> On Thu, Apr 21, 2022 at 9:54 AM Manoj VM  wrote:
>>
>>> ...  I have done the troubleshooting and found that the Liquibase
>>> changes are part of 1.6 tag.
>>>
>>> Ref
>>> https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java
>>>
>>>
>>> We have taken a workaround to do migration to commit prior to this
>>> change first, and then migrate to 1.6.  it is a long short.  Any other
>>> suggestions are welcome.
>>>
>>> Thanks,
>>> Manoj
>>>
>>> On Thu, 21 Apr, 2022, 03:49 Aleksandar Vidakovic, <
>>> chee...@monkeysintown.com> wrote:
>>>
 so, are you dropping the schema_version table yourself or is Liquibase
 doing that? Latter would be kind of plausible, because why keep it if
 there's no more Flyway; and overall this shouldn't influence anything
 here... the migration failures are a bit of a surprise here though (this
 was tested quite extensively) could you send stacktraces or similar to
 get an idea where exactly things seem to break on your end? I suspect
 there's something else going on... unless we have more people with similar
 issues? But again, the first time I've heard it now... maybe we can sort it
 out here... if it's affecting a broader audience then we have to crank out
 a patch release with a fix.

 ... if you could send the errors here then we can see how we can get
 this fixed for you or find any other workaround.

 Cheers,

 Aleks

 On Wed, Apr 20, 2022 at 6:24 PM Aleksandar Vidakovic <
 chee...@monkeysintown.com> wrote:

> ... first time I heard it... Kelvin: are we sure that there was no
> quick pull from the develop branch and that got started at one point? I
> know that this kind of "upgrade" is quite popular, but this doesn't really
> fly anymore with the mechanics in place.
>
> On Wed, Apr 20, 2022 at 5:02 PM Arnold Galovics <
> galovicsarn...@gmail.com> wrote:
>
>> Hi,
>>
>> It's strange because the 1.6 version shouldn't include Liquibase. We
>> only wanted to release it after 1.6.
>>
>> @Aleks, did we mix it up somehow?
>>
>> Best,
>> Arnold
>>
>> On Tue, Apr 19, 2022 at 4:59 PM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> @Arnold could you chime in here and help Manoj?
>>>
>>> On Tue, Apr 19, 2022 at 12:38 PM Manoj VM  wrote:
>>>
 Hi Aleksandar Vidakovic,

 Is there any update that happened to the 1.6 release?

 We are getting *"SchemaUpgradeNeededException: Make sure to
 upgrade to Fineract 1.6 first and then to a newer version"* error
 while upgrading to *tag 1.6*

 ref:
 https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java

 Thanks and Regards,
 Manoj
 fynarfin.io


 On Tue, Mar 8, 2022 at 10:52 AM Kelvin Ikome 
 wrote:

> Okay,
>
> Thanks, Aleks, Arnold.
>
> We have begun the work for 1.6 tag
>
> On Mon, Mar 7, 2022 at 10:55 AM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi Kelvin,
>>
>> ... you can't do that anymore (pu

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Arnold Galovics]

Hey guys,

I'm not really sure what happened, maybe we mistagged the release by a
single commit because the original idea was definitely that the 1.6 release
will be the latest one doing the database migrations using Flyway.

Could we retag the previous commit (what Manoj used) with 1.6 and drop the
current one? What are the implications there?

Best,
Arnold

On Thu, Apr 21, 2022 at 7:58 PM James Dailey  wrote:

> Manoj
>
> Thanks for digging into that.
>
> Yes, the TenantDatabaseUpgradeService.java file is in the release
> source code Zip file with the liquibase migration on Upgrade.
>
> @Aleksandar Vidakovic   I think we want to be
> even more clear about the migration path.
>
> I believe that release 1.6 was aiming to be the last version that used
> Flyway to upgrade to the 1.6 version.  ??
> Thereafter, the requirement would be to drop Flyway and use Liquibase for
> both migrations and database independence.
>
>  applyInitialLiquidbase() is something to be triggered once running on
> 1.6?
>
> I'm probably not following the logic well enough.  So, please correct me.
>
>
>
> On Thu, Apr 21, 2022 at 9:54 AM Manoj VM  wrote:
>
>> ...  I have done the troubleshooting and found that the Liquibase changes
>> are part of 1.6 tag.
>>
>> Ref
>> https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java
>>
>>
>> We have taken a workaround to do migration to commit prior to this change
>> first, and then migrate to 1.6.  it is a long short.  Any other suggestions
>> are welcome.
>>
>> Thanks,
>> Manoj
>>
>> On Thu, 21 Apr, 2022, 03:49 Aleksandar Vidakovic, <
>> chee...@monkeysintown.com> wrote:
>>
>>> so, are you dropping the schema_version table yourself or is Liquibase
>>> doing that? Latter would be kind of plausible, because why keep it if
>>> there's no more Flyway; and overall this shouldn't influence anything
>>> here... the migration failures are a bit of a surprise here though (this
>>> was tested quite extensively) could you send stacktraces or similar to
>>> get an idea where exactly things seem to break on your end? I suspect
>>> there's something else going on... unless we have more people with similar
>>> issues? But again, the first time I've heard it now... maybe we can sort it
>>> out here... if it's affecting a broader audience then we have to crank out
>>> a patch release with a fix.
>>>
>>> ... if you could send the errors here then we can see how we can get
>>> this fixed for you or find any other workaround.
>>>
>>> Cheers,
>>>
>>> Aleks
>>>
>>> On Wed, Apr 20, 2022 at 6:24 PM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 ... first time I heard it... Kelvin: are we sure that there was no
 quick pull from the develop branch and that got started at one point? I
 know that this kind of "upgrade" is quite popular, but this doesn't really
 fly anymore with the mechanics in place.

 On Wed, Apr 20, 2022 at 5:02 PM Arnold Galovics <
 galovicsarn...@gmail.com> wrote:

> Hi,
>
> It's strange because the 1.6 version shouldn't include Liquibase. We
> only wanted to release it after 1.6.
>
> @Aleks, did we mix it up somehow?
>
> Best,
> Arnold
>
> On Tue, Apr 19, 2022 at 4:59 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> @Arnold could you chime in here and help Manoj?
>>
>> On Tue, Apr 19, 2022 at 12:38 PM Manoj VM  wrote:
>>
>>> Hi Aleksandar Vidakovic,
>>>
>>> Is there any update that happened to the 1.6 release?
>>>
>>> We are getting *"SchemaUpgradeNeededException: Make sure to upgrade
>>> to Fineract 1.6 first and then to a newer version"* error while
>>> upgrading to *tag 1.6*
>>>
>>> ref:
>>> https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java
>>>
>>> Thanks and Regards,
>>> Manoj
>>> fynarfin.io
>>>
>>>
>>> On Tue, Mar 8, 2022 at 10:52 AM Kelvin Ikome 
>>> wrote:
>>>
 Okay,

 Thanks, Aleks, Arnold.

 We have begun the work for 1.6 tag

 On Mon, Mar 7, 2022 at 10:55 AM Aleksandar Vidakovic <
 chee...@monkeysintown.com> wrote:

> Hi Kelvin,
>
> ... you can't do that anymore (pulling from develop
> immediately)... you have to first upgrade your instance (aka database
> schema with Fineract 1.6.0... the release that is... exactly that
> version)... and only after that you can do the upgrade with the 
> current
> develop branch (we try to keep this as error free as possible, but 
> develop
> is considered unstable until we release).
>
> Hope that helps.
>
> Cheers,
>

Re: Fineract 1.5.0 to 1.6.0 upgrade

[James Dailey]

Manoj

Thanks for digging into that.

Yes, the TenantDatabaseUpgradeService.java file is in the release
source code Zip file with the liquibase migration on Upgrade.

@Aleksandar Vidakovic   I think we want to be
even more clear about the migration path.

I believe that release 1.6 was aiming to be the last version that used
Flyway to upgrade to the 1.6 version.  ??
Thereafter, the requirement would be to drop Flyway and use Liquibase for
both migrations and database independence.

 applyInitialLiquidbase() is something to be triggered once running on 1.6?

I'm probably not following the logic well enough.  So, please correct me.



On Thu, Apr 21, 2022 at 9:54 AM Manoj VM  wrote:

> ...  I have done the troubleshooting and found that the Liquibase changes
> are part of 1.6 tag.
>
> Ref
> https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java
>
>
> We have taken a workaround to do migration to commit prior to this change
> first, and then migrate to 1.6.  it is a long short.  Any other suggestions
> are welcome.
>
> Thanks,
> Manoj
>
> On Thu, 21 Apr, 2022, 03:49 Aleksandar Vidakovic, <
> chee...@monkeysintown.com> wrote:
>
>> so, are you dropping the schema_version table yourself or is Liquibase
>> doing that? Latter would be kind of plausible, because why keep it if
>> there's no more Flyway; and overall this shouldn't influence anything
>> here... the migration failures are a bit of a surprise here though (this
>> was tested quite extensively) could you send stacktraces or similar to
>> get an idea where exactly things seem to break on your end? I suspect
>> there's something else going on... unless we have more people with similar
>> issues? But again, the first time I've heard it now... maybe we can sort it
>> out here... if it's affecting a broader audience then we have to crank out
>> a patch release with a fix.
>>
>> ... if you could send the errors here then we can see how we can get this
>> fixed for you or find any other workaround.
>>
>> Cheers,
>>
>> Aleks
>>
>> On Wed, Apr 20, 2022 at 6:24 PM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> ... first time I heard it... Kelvin: are we sure that there was no quick
>>> pull from the develop branch and that got started at one point? I know that
>>> this kind of "upgrade" is quite popular, but this doesn't really fly
>>> anymore with the mechanics in place.
>>>
>>> On Wed, Apr 20, 2022 at 5:02 PM Arnold Galovics <
>>> galovicsarn...@gmail.com> wrote:
>>>
 Hi,

 It's strange because the 1.6 version shouldn't include Liquibase. We
 only wanted to release it after 1.6.

 @Aleks, did we mix it up somehow?

 Best,
 Arnold

 On Tue, Apr 19, 2022 at 4:59 PM Aleksandar Vidakovic <
 chee...@monkeysintown.com> wrote:

> @Arnold could you chime in here and help Manoj?
>
> On Tue, Apr 19, 2022 at 12:38 PM Manoj VM  wrote:
>
>> Hi Aleksandar Vidakovic,
>>
>> Is there any update that happened to the 1.6 release?
>>
>> We are getting *"SchemaUpgradeNeededException: Make sure to upgrade
>> to Fineract 1.6 first and then to a newer version"* error while
>> upgrading to *tag 1.6*
>>
>> ref:
>> https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java
>>
>> Thanks and Regards,
>> Manoj
>> fynarfin.io
>>
>>
>> On Tue, Mar 8, 2022 at 10:52 AM Kelvin Ikome 
>> wrote:
>>
>>> Okay,
>>>
>>> Thanks, Aleks, Arnold.
>>>
>>> We have begun the work for 1.6 tag
>>>
>>> On Mon, Mar 7, 2022 at 10:55 AM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 Hi Kelvin,

 ... you can't do that anymore (pulling from develop immediately)...
 you have to first upgrade your instance (aka database schema with 
 Fineract
 1.6.0... the release that is... exactly that version)... and only after
 that you can do the upgrade with the current develop branch (we try to 
 keep
 this as error free as possible, but develop is considered unstable 
 until we
 release).

 Hope that helps.

 Cheers,

 Aleks

 On Mon, Mar 7, 2022 at 10:15 AM Kelvin Ikome 
 wrote:

> Hi Arnold,
>
> We pulled in from the develop branch
>
> On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics <
> galovicsarn...@gmail.com> wrote:
>
>> Hi Kelvin, Sifiso,
>>
>> *Kelvin: *
>> Could you please share a little more info which version of
>> Fineract you're trying to use?
>>
>> The thing is, the latest release version (1.6.0) doe

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Manoj VM]

...  I have done the troubleshooting and found that the Liquibase changes
are part of 1.6 tag.

Ref
https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java


We have taken a workaround to do migration to commit prior to this change
first, and then migrate to 1.6.  it is a long short.  Any other suggestions
are welcome.

Thanks,
Manoj

On Thu, 21 Apr, 2022, 03:49 Aleksandar Vidakovic, 
wrote:

> so, are you dropping the schema_version table yourself or is Liquibase
> doing that? Latter would be kind of plausible, because why keep it if
> there's no more Flyway; and overall this shouldn't influence anything
> here... the migration failures are a bit of a surprise here though (this
> was tested quite extensively) could you send stacktraces or similar to
> get an idea where exactly things seem to break on your end? I suspect
> there's something else going on... unless we have more people with similar
> issues? But again, the first time I've heard it now... maybe we can sort it
> out here... if it's affecting a broader audience then we have to crank out
> a patch release with a fix.
>
> ... if you could send the errors here then we can see how we can get this
> fixed for you or find any other workaround.
>
> Cheers,
>
> Aleks
>
> On Wed, Apr 20, 2022 at 6:24 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> ... first time I heard it... Kelvin: are we sure that there was no quick
>> pull from the develop branch and that got started at one point? I know that
>> this kind of "upgrade" is quite popular, but this doesn't really fly
>> anymore with the mechanics in place.
>>
>> On Wed, Apr 20, 2022 at 5:02 PM Arnold Galovics 
>> wrote:
>>
>>> Hi,
>>>
>>> It's strange because the 1.6 version shouldn't include Liquibase. We
>>> only wanted to release it after 1.6.
>>>
>>> @Aleks, did we mix it up somehow?
>>>
>>> Best,
>>> Arnold
>>>
>>> On Tue, Apr 19, 2022 at 4:59 PM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 @Arnold could you chime in here and help Manoj?

 On Tue, Apr 19, 2022 at 12:38 PM Manoj VM  wrote:

> Hi Aleksandar Vidakovic,
>
> Is there any update that happened to the 1.6 release?
>
> We are getting *"SchemaUpgradeNeededException: Make sure to upgrade
> to Fineract 1.6 first and then to a newer version"* error while
> upgrading to *tag 1.6*
>
> ref:
> https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java
>
> Thanks and Regards,
> Manoj
> fynarfin.io
>
>
> On Tue, Mar 8, 2022 at 10:52 AM Kelvin Ikome 
> wrote:
>
>> Okay,
>>
>> Thanks, Aleks, Arnold.
>>
>> We have begun the work for 1.6 tag
>>
>> On Mon, Mar 7, 2022 at 10:55 AM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> Hi Kelvin,
>>>
>>> ... you can't do that anymore (pulling from develop immediately)...
>>> you have to first upgrade your instance (aka database schema with 
>>> Fineract
>>> 1.6.0... the release that is... exactly that version)... and only after
>>> that you can do the upgrade with the current develop branch (we try to 
>>> keep
>>> this as error free as possible, but develop is considered unstable 
>>> until we
>>> release).
>>>
>>> Hope that helps.
>>>
>>> Cheers,
>>>
>>> Aleks
>>>
>>> On Mon, Mar 7, 2022 at 10:15 AM Kelvin Ikome 
>>> wrote:
>>>
 Hi Arnold,

 We pulled in from the develop branch

 On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics <
 galovicsarn...@gmail.com> wrote:

> Hi Kelvin, Sifiso,
>
> *Kelvin: *
> Could you please share a little more info which version of
> Fineract you're trying to use?
>
> The thing is, the latest release version (1.6.0) doesn't have
> Liquibase at all, it still runs Flyway migrations. Only the develop 
> branch
> (later to be 1.7.0) got switched to Liquibase.
>
> *Sifiso:*
> Could you please start another thread on your problems? A database
> upgrade seems to be another thing to take care of. Also, make sure to 
> share
> the kind of errors you're experiencing.
>
> Best,
> Arnold
>
> On Mon, Mar 7, 2022 at 8:59 AM  wrote:
>
>> Hi Kelvin,
>>
>>
>>
>> We are actually in the same predicament as you. However we have
>> upgraded our database from MySQL 5.7 as advised to MariaDB 10.6. If 
>> we use
>> data from version 18.03.01 it fails to migrate our data. If we use
>> databases running on 1.5.0 release it

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Aleksandar Vidakovic]

so, are you dropping the schema_version table yourself or is Liquibase
doing that? Latter would be kind of plausible, because why keep it if
there's no more Flyway; and overall this shouldn't influence anything
here... the migration failures are a bit of a surprise here though (this
was tested quite extensively) could you send stacktraces or similar to
get an idea where exactly things seem to break on your end? I suspect
there's something else going on... unless we have more people with similar
issues? But again, the first time I've heard it now... maybe we can sort it
out here... if it's affecting a broader audience then we have to crank out
a patch release with a fix.

... if you could send the errors here then we can see how we can get this
fixed for you or find any other workaround.

Cheers,

Aleks

On Wed, Apr 20, 2022 at 6:24 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> ... first time I heard it... Kelvin: are we sure that there was no quick
> pull from the develop branch and that got started at one point? I know that
> this kind of "upgrade" is quite popular, but this doesn't really fly
> anymore with the mechanics in place.
>
> On Wed, Apr 20, 2022 at 5:02 PM Arnold Galovics 
> wrote:
>
>> Hi,
>>
>> It's strange because the 1.6 version shouldn't include Liquibase. We only
>> wanted to release it after 1.6.
>>
>> @Aleks, did we mix it up somehow?
>>
>> Best,
>> Arnold
>>
>> On Tue, Apr 19, 2022 at 4:59 PM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> @Arnold could you chime in here and help Manoj?
>>>
>>> On Tue, Apr 19, 2022 at 12:38 PM Manoj VM  wrote:
>>>
 Hi Aleksandar Vidakovic,

 Is there any update that happened to the 1.6 release?

 We are getting *"SchemaUpgradeNeededException: Make sure to upgrade to
 Fineract 1.6 first and then to a newer version"* error while upgrading
 to *tag 1.6*

 ref:
 https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java

 Thanks and Regards,
 Manoj
 fynarfin.io


 On Tue, Mar 8, 2022 at 10:52 AM Kelvin Ikome 
 wrote:

> Okay,
>
> Thanks, Aleks, Arnold.
>
> We have begun the work for 1.6 tag
>
> On Mon, Mar 7, 2022 at 10:55 AM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi Kelvin,
>>
>> ... you can't do that anymore (pulling from develop immediately)...
>> you have to first upgrade your instance (aka database schema with 
>> Fineract
>> 1.6.0... the release that is... exactly that version)... and only after
>> that you can do the upgrade with the current develop branch (we try to 
>> keep
>> this as error free as possible, but develop is considered unstable until 
>> we
>> release).
>>
>> Hope that helps.
>>
>> Cheers,
>>
>> Aleks
>>
>> On Mon, Mar 7, 2022 at 10:15 AM Kelvin Ikome 
>> wrote:
>>
>>> Hi Arnold,
>>>
>>> We pulled in from the develop branch
>>>
>>> On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics <
>>> galovicsarn...@gmail.com> wrote:
>>>
 Hi Kelvin, Sifiso,

 *Kelvin: *
 Could you please share a little more info which version of Fineract
 you're trying to use?

 The thing is, the latest release version (1.6.0) doesn't have
 Liquibase at all, it still runs Flyway migrations. Only the develop 
 branch
 (later to be 1.7.0) got switched to Liquibase.

 *Sifiso:*
 Could you please start another thread on your problems? A database
 upgrade seems to be another thing to take care of. Also, make sure to 
 share
 the kind of errors you're experiencing.

 Best,
 Arnold

 On Mon, Mar 7, 2022 at 8:59 AM  wrote:

> Hi Kelvin,
>
>
>
> We are actually in the same predicament as you. However we have
> upgraded our database from MySQL 5.7 as advised to MariaDB 10.6. If 
> we use
> data from version 18.03.01 it fails to migrate our data. If we use
> databases running on 1.5.0 release it completes the startup but the 
> system
> login fails.
>
>
>
> Let’s hear from the others what challenges they’ve experienced,
> maybe there is a workaround already.
>
>
>
> Regards,
>
> Sifiso
>
>
>
> *From:* Kelvin Ikome 
> *Sent:* Monday, 07 March 2022 9:29 AM
> *To:* dev@fineract.apache.org
> *Subject:* Fineract 1.5.0 to 1.6.0 upgrade
>
>
>
> Hi everyone,
>
>
>
> We have upgraded from Fineract 1.5.0 to 1.6.0.
>
>>>

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Aleksandar Vidakovic]

... first time I heard it... Kelvin: are we sure that there was no quick
pull from the develop branch and that got started at one point? I know that
this kind of "upgrade" is quite popular, but this doesn't really fly
anymore with the mechanics in place.

On Wed, Apr 20, 2022 at 5:02 PM Arnold Galovics 
wrote:

> Hi,
>
> It's strange because the 1.6 version shouldn't include Liquibase. We only
> wanted to release it after 1.6.
>
> @Aleks, did we mix it up somehow?
>
> Best,
> Arnold
>
> On Tue, Apr 19, 2022 at 4:59 PM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> @Arnold could you chime in here and help Manoj?
>>
>> On Tue, Apr 19, 2022 at 12:38 PM Manoj VM  wrote:
>>
>>> Hi Aleksandar Vidakovic,
>>>
>>> Is there any update that happened to the 1.6 release?
>>>
>>> We are getting *"SchemaUpgradeNeededException: Make sure to upgrade to
>>> Fineract 1.6 first and then to a newer version"* error while upgrading
>>> to *tag 1.6*
>>>
>>> ref:
>>> https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java
>>>
>>> Thanks and Regards,
>>> Manoj
>>> fynarfin.io
>>>
>>>
>>> On Tue, Mar 8, 2022 at 10:52 AM Kelvin Ikome  wrote:
>>>
 Okay,

 Thanks, Aleks, Arnold.

 We have begun the work for 1.6 tag

 On Mon, Mar 7, 2022 at 10:55 AM Aleksandar Vidakovic <
 chee...@monkeysintown.com> wrote:

> Hi Kelvin,
>
> ... you can't do that anymore (pulling from develop immediately)...
> you have to first upgrade your instance (aka database schema with Fineract
> 1.6.0... the release that is... exactly that version)... and only after
> that you can do the upgrade with the current develop branch (we try to 
> keep
> this as error free as possible, but develop is considered unstable until 
> we
> release).
>
> Hope that helps.
>
> Cheers,
>
> Aleks
>
> On Mon, Mar 7, 2022 at 10:15 AM Kelvin Ikome 
> wrote:
>
>> Hi Arnold,
>>
>> We pulled in from the develop branch
>>
>> On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics <
>> galovicsarn...@gmail.com> wrote:
>>
>>> Hi Kelvin, Sifiso,
>>>
>>> *Kelvin: *
>>> Could you please share a little more info which version of Fineract
>>> you're trying to use?
>>>
>>> The thing is, the latest release version (1.6.0) doesn't have
>>> Liquibase at all, it still runs Flyway migrations. Only the develop 
>>> branch
>>> (later to be 1.7.0) got switched to Liquibase.
>>>
>>> *Sifiso:*
>>> Could you please start another thread on your problems? A database
>>> upgrade seems to be another thing to take care of. Also, make sure to 
>>> share
>>> the kind of errors you're experiencing.
>>>
>>> Best,
>>> Arnold
>>>
>>> On Mon, Mar 7, 2022 at 8:59 AM  wrote:
>>>
 Hi Kelvin,



 We are actually in the same predicament as you. However we have
 upgraded our database from MySQL 5.7 as advised to MariaDB 10.6. If we 
 use
 data from version 18.03.01 it fails to migrate our data. If we use
 databases running on 1.5.0 release it completes the startup but the 
 system
 login fails.



 Let’s hear from the others what challenges they’ve experienced,
 maybe there is a workaround already.



 Regards,

 Sifiso



 *From:* Kelvin Ikome 
 *Sent:* Monday, 07 March 2022 9:29 AM
 *To:* dev@fineract.apache.org
 *Subject:* Fineract 1.5.0 to 1.6.0 upgrade



 Hi everyone,



 We have upgraded from Fineract 1.5.0 to 1.6.0.

 After dropping the flyway migrations table (schema_version),
 Liquibase runs it's own migrations which fails (in recreating tables 
 which
 already exist) because we are aiming to re-use DB with existing data 
 from
 Fineract 1.5.0.



 Any ideas on how to address this would be greatly appreciated.



 Kind regards



 --

 *Kelvin Ikome*
 Chief Executive Officer

 [image: facebook icon]  [image:
 twitter icon]  [image: youtube
 icon]  
 [image:
 linkedin icon] 


 *t:*
 *m:*
 *e:*
 *a:*

 +(237) 677-666-659
 kel...@ciniter.com
 Ciniter, Molyko, Buea, South West, Cameroon
 *www.ciniter.com* 

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Arnold Galovics]

Hi,

It's strange because the 1.6 version shouldn't include Liquibase. We only
wanted to release it after 1.6.

@Aleks, did we mix it up somehow?

Best,
Arnold

On Tue, Apr 19, 2022 at 4:59 PM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> @Arnold could you chime in here and help Manoj?
>
> On Tue, Apr 19, 2022 at 12:38 PM Manoj VM  wrote:
>
>> Hi Aleksandar Vidakovic,
>>
>> Is there any update that happened to the 1.6 release?
>>
>> We are getting *"SchemaUpgradeNeededException: Make sure to upgrade to
>> Fineract 1.6 first and then to a newer version"* error while upgrading
>> to *tag 1.6*
>>
>> ref:
>> https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java
>>
>> Thanks and Regards,
>> Manoj
>> fynarfin.io
>>
>>
>> On Tue, Mar 8, 2022 at 10:52 AM Kelvin Ikome  wrote:
>>
>>> Okay,
>>>
>>> Thanks, Aleks, Arnold.
>>>
>>> We have begun the work for 1.6 tag
>>>
>>> On Mon, Mar 7, 2022 at 10:55 AM Aleksandar Vidakovic <
>>> chee...@monkeysintown.com> wrote:
>>>
 Hi Kelvin,

 ... you can't do that anymore (pulling from develop immediately)... you
 have to first upgrade your instance (aka database schema with Fineract
 1.6.0... the release that is... exactly that version)... and only after
 that you can do the upgrade with the current develop branch (we try to keep
 this as error free as possible, but develop is considered unstable until we
 release).

 Hope that helps.

 Cheers,

 Aleks

 On Mon, Mar 7, 2022 at 10:15 AM Kelvin Ikome 
 wrote:

> Hi Arnold,
>
> We pulled in from the develop branch
>
> On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics <
> galovicsarn...@gmail.com> wrote:
>
>> Hi Kelvin, Sifiso,
>>
>> *Kelvin: *
>> Could you please share a little more info which version of Fineract
>> you're trying to use?
>>
>> The thing is, the latest release version (1.6.0) doesn't have
>> Liquibase at all, it still runs Flyway migrations. Only the develop 
>> branch
>> (later to be 1.7.0) got switched to Liquibase.
>>
>> *Sifiso:*
>> Could you please start another thread on your problems? A database
>> upgrade seems to be another thing to take care of. Also, make sure to 
>> share
>> the kind of errors you're experiencing.
>>
>> Best,
>> Arnold
>>
>> On Mon, Mar 7, 2022 at 8:59 AM  wrote:
>>
>>> Hi Kelvin,
>>>
>>>
>>>
>>> We are actually in the same predicament as you. However we have
>>> upgraded our database from MySQL 5.7 as advised to MariaDB 10.6. If we 
>>> use
>>> data from version 18.03.01 it fails to migrate our data. If we use
>>> databases running on 1.5.0 release it completes the startup but the 
>>> system
>>> login fails.
>>>
>>>
>>>
>>> Let’s hear from the others what challenges they’ve experienced,
>>> maybe there is a workaround already.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Sifiso
>>>
>>>
>>>
>>> *From:* Kelvin Ikome 
>>> *Sent:* Monday, 07 March 2022 9:29 AM
>>> *To:* dev@fineract.apache.org
>>> *Subject:* Fineract 1.5.0 to 1.6.0 upgrade
>>>
>>>
>>>
>>> Hi everyone,
>>>
>>>
>>>
>>> We have upgraded from Fineract 1.5.0 to 1.6.0.
>>>
>>> After dropping the flyway migrations table (schema_version),
>>> Liquibase runs it's own migrations which fails (in recreating tables 
>>> which
>>> already exist) because we are aiming to re-use DB with existing data 
>>> from
>>> Fineract 1.5.0.
>>>
>>>
>>>
>>> Any ideas on how to address this would be greatly appreciated.
>>>
>>>
>>>
>>> Kind regards
>>>
>>>
>>>
>>> --
>>>
>>> *Kelvin Ikome*
>>> Chief Executive Officer
>>>
>>> [image: facebook icon]  [image:
>>> twitter icon]  [image: youtube
>>> icon]  [image:
>>> linkedin icon] 
>>>
>>>
>>> *t:*
>>> *m:*
>>> *e:*
>>> *a:*
>>>
>>> +(237) 677-666-659
>>> kel...@ciniter.com
>>> Ciniter, Molyko, Buea, South West, Cameroon
>>> *www.ciniter.com* 
>>>
>>>
>>>
>>
>
> --
> Kelvin Ikome
> Chief Executive Officer [image: facebook icon]
>  [image: twitter icon]
>  [image: youtube icon]
>  [image:
> linkedin icon] 
>
>
> t:
> m:
> e:
> a: +(237) 677-666-659
> kel...@ciniter.com
> Cin

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Aleksandar Vidakovic]

@Arnold could you chime in here and help Manoj?

On Tue, Apr 19, 2022 at 12:38 PM Manoj VM  wrote:

> Hi Aleksandar Vidakovic,
>
> Is there any update that happened to the 1.6 release?
>
> We are getting *"SchemaUpgradeNeededException: Make sure to upgrade to
> Fineract 1.6 first and then to a newer version"* error while upgrading to *tag
> 1.6*
>
> ref:
> https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java
>
> Thanks and Regards,
> Manoj
> fynarfin.io
>
>
> On Tue, Mar 8, 2022 at 10:52 AM Kelvin Ikome  wrote:
>
>> Okay,
>>
>> Thanks, Aleks, Arnold.
>>
>> We have begun the work for 1.6 tag
>>
>> On Mon, Mar 7, 2022 at 10:55 AM Aleksandar Vidakovic <
>> chee...@monkeysintown.com> wrote:
>>
>>> Hi Kelvin,
>>>
>>> ... you can't do that anymore (pulling from develop immediately)... you
>>> have to first upgrade your instance (aka database schema with Fineract
>>> 1.6.0... the release that is... exactly that version)... and only after
>>> that you can do the upgrade with the current develop branch (we try to keep
>>> this as error free as possible, but develop is considered unstable until we
>>> release).
>>>
>>> Hope that helps.
>>>
>>> Cheers,
>>>
>>> Aleks
>>>
>>> On Mon, Mar 7, 2022 at 10:15 AM Kelvin Ikome  wrote:
>>>
 Hi Arnold,

 We pulled in from the develop branch

 On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics <
 galovicsarn...@gmail.com> wrote:

> Hi Kelvin, Sifiso,
>
> *Kelvin: *
> Could you please share a little more info which version of Fineract
> you're trying to use?
>
> The thing is, the latest release version (1.6.0) doesn't have
> Liquibase at all, it still runs Flyway migrations. Only the develop branch
> (later to be 1.7.0) got switched to Liquibase.
>
> *Sifiso:*
> Could you please start another thread on your problems? A database
> upgrade seems to be another thing to take care of. Also, make sure to 
> share
> the kind of errors you're experiencing.
>
> Best,
> Arnold
>
> On Mon, Mar 7, 2022 at 8:59 AM  wrote:
>
>> Hi Kelvin,
>>
>>
>>
>> We are actually in the same predicament as you. However we have
>> upgraded our database from MySQL 5.7 as advised to MariaDB 10.6. If we 
>> use
>> data from version 18.03.01 it fails to migrate our data. If we use
>> databases running on 1.5.0 release it completes the startup but the 
>> system
>> login fails.
>>
>>
>>
>> Let’s hear from the others what challenges they’ve experienced, maybe
>> there is a workaround already.
>>
>>
>>
>> Regards,
>>
>> Sifiso
>>
>>
>>
>> *From:* Kelvin Ikome 
>> *Sent:* Monday, 07 March 2022 9:29 AM
>> *To:* dev@fineract.apache.org
>> *Subject:* Fineract 1.5.0 to 1.6.0 upgrade
>>
>>
>>
>> Hi everyone,
>>
>>
>>
>> We have upgraded from Fineract 1.5.0 to 1.6.0.
>>
>> After dropping the flyway migrations table (schema_version),
>> Liquibase runs it's own migrations which fails (in recreating tables 
>> which
>> already exist) because we are aiming to re-use DB with existing data from
>> Fineract 1.5.0.
>>
>>
>>
>> Any ideas on how to address this would be greatly appreciated.
>>
>>
>>
>> Kind regards
>>
>>
>>
>> --
>>
>> *Kelvin Ikome*
>> Chief Executive Officer
>>
>> [image: facebook icon]  [image:
>> twitter icon]  [image: youtube icon]
>>  [image:
>> linkedin icon] 
>>
>>
>> *t:*
>> *m:*
>> *e:*
>> *a:*
>>
>> +(237) 677-666-659
>> kel...@ciniter.com
>> Ciniter, Molyko, Buea, South West, Cameroon
>> *www.ciniter.com* 
>>
>>
>>
>

 --
 Kelvin Ikome
 Chief Executive Officer [image: facebook icon]
  [image: twitter icon]
  [image: youtube icon]
  [image:
 linkedin icon] 


 t:
 m:
 e:
 a: +(237) 677-666-659
 kel...@ciniter.com
 Ciniter, Molyko, Buea, South West, Cameroon
 www.ciniter.com

>>>
>>
>> --
>> Kelvin Ikome
>> Chief Executive Officer [image: facebook icon]
>>  [image: twitter icon]
>>  [image: youtube icon]
>>  [image:
>> linkedin icon] 
>>
>>
>> t:
>> m:
>> e:
>> a: +(237) 677-666-

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Manoj VM]

Hi Aleksandar Vidakovic,

Is there any update that happened to the 1.6 release?

We are getting *"SchemaUpgradeNeededException: Make sure to upgrade to
Fineract 1.6 first and then to a newer version"* error while upgrading to *tag
1.6*

ref:
https://github.com/apache/fineract/blob/1.6.0/fineract-provider/src/main/java/org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.java

Thanks and Regards,
Manoj
fynarfin.io


On Tue, Mar 8, 2022 at 10:52 AM Kelvin Ikome  wrote:

> Okay,
>
> Thanks, Aleks, Arnold.
>
> We have begun the work for 1.6 tag
>
> On Mon, Mar 7, 2022 at 10:55 AM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> Hi Kelvin,
>>
>> ... you can't do that anymore (pulling from develop immediately)... you
>> have to first upgrade your instance (aka database schema with Fineract
>> 1.6.0... the release that is... exactly that version)... and only after
>> that you can do the upgrade with the current develop branch (we try to keep
>> this as error free as possible, but develop is considered unstable until we
>> release).
>>
>> Hope that helps.
>>
>> Cheers,
>>
>> Aleks
>>
>> On Mon, Mar 7, 2022 at 10:15 AM Kelvin Ikome  wrote:
>>
>>> Hi Arnold,
>>>
>>> We pulled in from the develop branch
>>>
>>> On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics <
>>> galovicsarn...@gmail.com> wrote:
>>>
 Hi Kelvin, Sifiso,

 *Kelvin: *
 Could you please share a little more info which version of Fineract
 you're trying to use?

 The thing is, the latest release version (1.6.0) doesn't have Liquibase
 at all, it still runs Flyway migrations. Only the develop branch (later to
 be 1.7.0) got switched to Liquibase.

 *Sifiso:*
 Could you please start another thread on your problems? A database
 upgrade seems to be another thing to take care of. Also, make sure to share
 the kind of errors you're experiencing.

 Best,
 Arnold

 On Mon, Mar 7, 2022 at 8:59 AM  wrote:

> Hi Kelvin,
>
>
>
> We are actually in the same predicament as you. However we have
> upgraded our database from MySQL 5.7 as advised to MariaDB 10.6. If we use
> data from version 18.03.01 it fails to migrate our data. If we use
> databases running on 1.5.0 release it completes the startup but the system
> login fails.
>
>
>
> Let’s hear from the others what challenges they’ve experienced, maybe
> there is a workaround already.
>
>
>
> Regards,
>
> Sifiso
>
>
>
> *From:* Kelvin Ikome 
> *Sent:* Monday, 07 March 2022 9:29 AM
> *To:* dev@fineract.apache.org
> *Subject:* Fineract 1.5.0 to 1.6.0 upgrade
>
>
>
> Hi everyone,
>
>
>
> We have upgraded from Fineract 1.5.0 to 1.6.0.
>
> After dropping the flyway migrations table (schema_version), Liquibase
> runs it's own migrations which fails (in recreating tables which already
> exist) because we are aiming to re-use DB with existing data from Fineract
> 1.5.0.
>
>
>
> Any ideas on how to address this would be greatly appreciated.
>
>
>
> Kind regards
>
>
>
> --
>
> *Kelvin Ikome*
> Chief Executive Officer
>
> [image: facebook icon]  [image:
> twitter icon]  [image: youtube icon]
>  [image:
> linkedin icon] 
>
>
> *t:*
> *m:*
> *e:*
> *a:*
>
> +(237) 677-666-659
> kel...@ciniter.com
> Ciniter, Molyko, Buea, South West, Cameroon
> *www.ciniter.com* 
>
>
>

>>>
>>> --
>>> Kelvin Ikome
>>> Chief Executive Officer [image: facebook icon]
>>>  [image: twitter icon]
>>>  [image: youtube icon]
>>>  [image:
>>> linkedin icon] 
>>>
>>>
>>> t:
>>> m:
>>> e:
>>> a: +(237) 677-666-659
>>> kel...@ciniter.com
>>> Ciniter, Molyko, Buea, South West, Cameroon
>>> www.ciniter.com
>>>
>>
>
> --
> Kelvin Ikome
> Chief Executive Officer [image: facebook icon]
>  [image: twitter icon]
>  [image: youtube icon]
>  [image:
> linkedin icon] 
>
>
> t:
> m:
> e:
> a: +(237) 677-666-659
> kel...@ciniter.com
> Ciniter, Molyko, Buea, South West, Cameroon
> www.ciniter.com
>

-- 
Disclaimer:


Privileged & confidential information is contained in this 
message (including all attachments). If you are not an intended recipient 
of this message, please destroy this message immediately and kindly notify
t

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Kelvin Ikome]

Okay,

Thanks, Aleks, Arnold.

We have begun the work for 1.6 tag

On Mon, Mar 7, 2022 at 10:55 AM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Hi Kelvin,
>
> ... you can't do that anymore (pulling from develop immediately)... you
> have to first upgrade your instance (aka database schema with Fineract
> 1.6.0... the release that is... exactly that version)... and only after
> that you can do the upgrade with the current develop branch (we try to keep
> this as error free as possible, but develop is considered unstable until we
> release).
>
> Hope that helps.
>
> Cheers,
>
> Aleks
>
> On Mon, Mar 7, 2022 at 10:15 AM Kelvin Ikome  wrote:
>
>> Hi Arnold,
>>
>> We pulled in from the develop branch
>>
>> On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics 
>> wrote:
>>
>>> Hi Kelvin, Sifiso,
>>>
>>> *Kelvin: *
>>> Could you please share a little more info which version of Fineract
>>> you're trying to use?
>>>
>>> The thing is, the latest release version (1.6.0) doesn't have Liquibase
>>> at all, it still runs Flyway migrations. Only the develop branch (later to
>>> be 1.7.0) got switched to Liquibase.
>>>
>>> *Sifiso:*
>>> Could you please start another thread on your problems? A database
>>> upgrade seems to be another thing to take care of. Also, make sure to share
>>> the kind of errors you're experiencing.
>>>
>>> Best,
>>> Arnold
>>>
>>> On Mon, Mar 7, 2022 at 8:59 AM  wrote:
>>>
 Hi Kelvin,



 We are actually in the same predicament as you. However we have
 upgraded our database from MySQL 5.7 as advised to MariaDB 10.6. If we use
 data from version 18.03.01 it fails to migrate our data. If we use
 databases running on 1.5.0 release it completes the startup but the system
 login fails.



 Let’s hear from the others what challenges they’ve experienced, maybe
 there is a workaround already.



 Regards,

 Sifiso



 *From:* Kelvin Ikome 
 *Sent:* Monday, 07 March 2022 9:29 AM
 *To:* dev@fineract.apache.org
 *Subject:* Fineract 1.5.0 to 1.6.0 upgrade



 Hi everyone,



 We have upgraded from Fineract 1.5.0 to 1.6.0.

 After dropping the flyway migrations table (schema_version), Liquibase
 runs it's own migrations which fails (in recreating tables which already
 exist) because we are aiming to re-use DB with existing data from Fineract
 1.5.0.



 Any ideas on how to address this would be greatly appreciated.



 Kind regards



 --

 *Kelvin Ikome*
 Chief Executive Officer

 [image: facebook icon]  [image:
 twitter icon]  [image: youtube icon]
  [image:
 linkedin icon] 


 *t:*
 *m:*
 *e:*
 *a:*

 +(237) 677-666-659
 kel...@ciniter.com
 Ciniter, Molyko, Buea, South West, Cameroon
 *www.ciniter.com* 



>>>
>>
>> --
>> Kelvin Ikome
>> Chief Executive Officer [image: facebook icon]
>>  [image: twitter icon]
>>  [image: youtube icon]
>>  [image:
>> linkedin icon] 
>>
>>
>> t:
>> m:
>> e:
>> a: +(237) 677-666-659
>> kel...@ciniter.com
>> Ciniter, Molyko, Buea, South West, Cameroon
>> www.ciniter.com
>>
>

-- 
Kelvin Ikome
Chief Executive Officer [image: facebook icon]
 [image: twitter icon]
 [image: youtube icon]
 [image: linkedin
icon] 


t:
m:
e:
a: +(237) 677-666-659
kel...@ciniter.com
Ciniter, Molyko, Buea, South West, Cameroon
www.ciniter.com

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Aleksandar Vidakovic]

Hi Kelvin,

... you can't do that anymore (pulling from develop immediately)... you
have to first upgrade your instance (aka database schema with Fineract
1.6.0... the release that is... exactly that version)... and only after
that you can do the upgrade with the current develop branch (we try to keep
this as error free as possible, but develop is considered unstable until we
release).

Hope that helps.

Cheers,

Aleks

On Mon, Mar 7, 2022 at 10:15 AM Kelvin Ikome  wrote:

> Hi Arnold,
>
> We pulled in from the develop branch
>
> On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics 
> wrote:
>
>> Hi Kelvin, Sifiso,
>>
>> *Kelvin: *
>> Could you please share a little more info which version of Fineract
>> you're trying to use?
>>
>> The thing is, the latest release version (1.6.0) doesn't have Liquibase
>> at all, it still runs Flyway migrations. Only the develop branch (later to
>> be 1.7.0) got switched to Liquibase.
>>
>> *Sifiso:*
>> Could you please start another thread on your problems? A database
>> upgrade seems to be another thing to take care of. Also, make sure to share
>> the kind of errors you're experiencing.
>>
>> Best,
>> Arnold
>>
>> On Mon, Mar 7, 2022 at 8:59 AM  wrote:
>>
>>> Hi Kelvin,
>>>
>>>
>>>
>>> We are actually in the same predicament as you. However we have upgraded
>>> our database from MySQL 5.7 as advised to MariaDB 10.6. If we use data from
>>> version 18.03.01 it fails to migrate our data. If we use databases running
>>> on 1.5.0 release it completes the startup but the system login fails.
>>>
>>>
>>>
>>> Let’s hear from the others what challenges they’ve experienced, maybe
>>> there is a workaround already.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Sifiso
>>>
>>>
>>>
>>> *From:* Kelvin Ikome 
>>> *Sent:* Monday, 07 March 2022 9:29 AM
>>> *To:* dev@fineract.apache.org
>>> *Subject:* Fineract 1.5.0 to 1.6.0 upgrade
>>>
>>>
>>>
>>> Hi everyone,
>>>
>>>
>>>
>>> We have upgraded from Fineract 1.5.0 to 1.6.0.
>>>
>>> After dropping the flyway migrations table (schema_version), Liquibase
>>> runs it's own migrations which fails (in recreating tables which already
>>> exist) because we are aiming to re-use DB with existing data from Fineract
>>> 1.5.0.
>>>
>>>
>>>
>>> Any ideas on how to address this would be greatly appreciated.
>>>
>>>
>>>
>>> Kind regards
>>>
>>>
>>>
>>> --
>>>
>>> *Kelvin Ikome*
>>> Chief Executive Officer
>>>
>>> [image: facebook icon]  [image:
>>> twitter icon]  [image: youtube icon]
>>>  [image:
>>> linkedin icon] 
>>>
>>>
>>> *t:*
>>> *m:*
>>> *e:*
>>> *a:*
>>>
>>> +(237) 677-666-659
>>> kel...@ciniter.com
>>> Ciniter, Molyko, Buea, South West, Cameroon
>>> *www.ciniter.com* 
>>>
>>>
>>>
>>
>
> --
> Kelvin Ikome
> Chief Executive Officer [image: facebook icon]
>  [image: twitter icon]
>  [image: youtube icon]
>  [image:
> linkedin icon] 
>
>
> t:
> m:
> e:
> a: +(237) 677-666-659
> kel...@ciniter.com
> Ciniter, Molyko, Buea, South West, Cameroon
> www.ciniter.com
>

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Kelvin Ikome]

Hi Arnold,

We pulled in from the develop branch

On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics 
wrote:

> Hi Kelvin, Sifiso,
>
> *Kelvin: *
> Could you please share a little more info which version of Fineract you're
> trying to use?
>
> The thing is, the latest release version (1.6.0) doesn't have Liquibase at
> all, it still runs Flyway migrations. Only the develop branch (later to be
> 1.7.0) got switched to Liquibase.
>
> *Sifiso:*
> Could you please start another thread on your problems? A database upgrade
> seems to be another thing to take care of. Also, make sure to share the
> kind of errors you're experiencing.
>
> Best,
> Arnold
>
> On Mon, Mar 7, 2022 at 8:59 AM  wrote:
>
>> Hi Kelvin,
>>
>>
>>
>> We are actually in the same predicament as you. However we have upgraded
>> our database from MySQL 5.7 as advised to MariaDB 10.6. If we use data from
>> version 18.03.01 it fails to migrate our data. If we use databases running
>> on 1.5.0 release it completes the startup but the system login fails.
>>
>>
>>
>> Let’s hear from the others what challenges they’ve experienced, maybe
>> there is a workaround already.
>>
>>
>>
>> Regards,
>>
>> Sifiso
>>
>>
>>
>> *From:* Kelvin Ikome 
>> *Sent:* Monday, 07 March 2022 9:29 AM
>> *To:* dev@fineract.apache.org
>> *Subject:* Fineract 1.5.0 to 1.6.0 upgrade
>>
>>
>>
>> Hi everyone,
>>
>>
>>
>> We have upgraded from Fineract 1.5.0 to 1.6.0.
>>
>> After dropping the flyway migrations table (schema_version), Liquibase
>> runs it's own migrations which fails (in recreating tables which already
>> exist) because we are aiming to re-use DB with existing data from Fineract
>> 1.5.0.
>>
>>
>>
>> Any ideas on how to address this would be greatly appreciated.
>>
>>
>>
>> Kind regards
>>
>>
>>
>> --
>>
>> *Kelvin Ikome*
>> Chief Executive Officer
>>
>> [image: facebook icon]  [image:
>> twitter icon]  [image: youtube icon]
>>  [image:
>> linkedin icon] 
>>
>>
>> *t:*
>> *m:*
>> *e:*
>> *a:*
>>
>> +(237) 677-666-659
>> kel...@ciniter.com
>> Ciniter, Molyko, Buea, South West, Cameroon
>> *www.ciniter.com* 
>>
>>
>>
>

-- 
Kelvin Ikome
Chief Executive Officer [image: facebook icon]
 [image: twitter icon]
 [image: youtube icon]
 [image: linkedin
icon] 


t:
m:
e:
a: +(237) 677-666-659
kel...@ciniter.com
Ciniter, Molyko, Buea, South West, Cameroon
www.ciniter.com

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Arnold Galovics]

Hi Kelvin, Sifiso,

*Kelvin: *
Could you please share a little more info which version of Fineract you're
trying to use?

The thing is, the latest release version (1.6.0) doesn't have Liquibase at
all, it still runs Flyway migrations. Only the develop branch (later to be
1.7.0) got switched to Liquibase.

*Sifiso:*
Could you please start another thread on your problems? A database upgrade
seems to be another thing to take care of. Also, make sure to share the
kind of errors you're experiencing.

Best,
Arnold

On Mon, Mar 7, 2022 at 8:59 AM  wrote:

> Hi Kelvin,
>
>
>
> We are actually in the same predicament as you. However we have upgraded
> our database from MySQL 5.7 as advised to MariaDB 10.6. If we use data from
> version 18.03.01 it fails to migrate our data. If we use databases running
> on 1.5.0 release it completes the startup but the system login fails.
>
>
>
> Let’s hear from the others what challenges they’ve experienced, maybe
> there is a workaround already.
>
>
>
> Regards,
>
> Sifiso
>
>
>
> *From:* Kelvin Ikome 
> *Sent:* Monday, 07 March 2022 9:29 AM
> *To:* dev@fineract.apache.org
> *Subject:* Fineract 1.5.0 to 1.6.0 upgrade
>
>
>
> Hi everyone,
>
>
>
> We have upgraded from Fineract 1.5.0 to 1.6.0.
>
> After dropping the flyway migrations table (schema_version), Liquibase
> runs it's own migrations which fails (in recreating tables which already
> exist) because we are aiming to re-use DB with existing data from Fineract
> 1.5.0.
>
>
>
> Any ideas on how to address this would be greatly appreciated.
>
>
>
> Kind regards
>
>
>
> --
>
> *Kelvin Ikome*
> Chief Executive Officer
>
> [image: facebook icon]  [image:
> twitter icon]  [image: youtube icon]
>  [image:
> linkedin icon] 
>
>
> *t:*
> *m:*
> *e:*
> *a:*
>
> +(237) 677-666-659
> kel...@ciniter.com
> Ciniter, Molyko, Buea, South West, Cameroon
> *www.ciniter.com* 
>
>
>

RE: Fineract 1.5.0 to 1.6.0 upgrade

[sifiso]

Hi Kelvin,

 

We are actually in the same predicament as you. However we have upgraded our 
database from MySQL 5.7 as advised to MariaDB 10.6. If we use data from version 
18.03.01 it fails to migrate our data. If we use databases running on 1.5.0 
release it completes the startup but the system login fails. 

 

Let’s hear from the others what challenges they’ve experienced, maybe there is 
a workaround already.

 

Regards,

Sifiso

 

From: Kelvin Ikome  
Sent: Monday, 07 March 2022 9:29 AM
To: dev@fineract.apache.org
Subject: Fineract 1.5.0 to 1.6.0 upgrade

 

Hi everyone,

 

We have upgraded from Fineract 1.5.0 to 1.6.0.

After dropping the flyway migrations table (schema_version), Liquibase runs 
it's own migrations which fails (in recreating tables which already exist) 
because we are aiming to re-use DB with existing data from Fineract 1.5.0.

 

Any ideas on how to address this would be greatly appreciated.

 

Kind regards

 

-- 


Kelvin Ikome
Chief Executive Officer

       
   
 




  

 

t:
m:
e:
a:

+(237) 677-666-659
kel...@ciniter.com  
Ciniter, Molyko, Buea, South West, Cameroon
  www.ciniter.com