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 <ma...@fynarfin.io> 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 <kel...@ciniter.com> >>>> 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 <kel...@ciniter.com> >>>>>> 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 <sif...@skyburgsystems.org> 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 <kel...@ciniter.com> >>>>>>>>> *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] <https://www.facebook.com/ciniter.ltd> [image: >>>>>>>>> twitter icon] <https://twitter.com/ciniter_ltd> [image: youtube >>>>>>>>> icon] <https://www.youtube.com/channel/UCfOgsIgX3l1TT4G79NBUt-A> >>>>>>>>> [image: >>>>>>>>> linkedin icon] <https://www.linkedin.com/company/ciniter> >>>>>>>>> >>>>>>>>> >>>>>>>>> *t:* >>>>>>>>> *m:* >>>>>>>>> *e:* >>>>>>>>> *a:* >>>>>>>>> >>>>>>>>> +(237) 677-666-659 >>>>>>>>> kel...@ciniter.com >>>>>>>>> Ciniter, Molyko, Buea, South West, Cameroon >>>>>>>>> *www.ciniter.com* <http://www.ciniter.com/> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Kelvin Ikome >>>>>>> Chief Executive Officer [image: facebook icon] >>>>>>> <https://www.facebook.com/ciniter.ltd> [image: twitter icon] >>>>>>> <https://twitter.com/ciniter_ltd> [image: youtube icon] >>>>>>> <https://www.youtube.com/channel/UCfOgsIgX3l1TT4G79NBUt-A> [image: >>>>>>> linkedin icon] <https://www.linkedin.com/company/ciniter> >>>>>>> >>>>>>> >>>>>>> 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] >>>>> <https://www.facebook.com/ciniter.ltd> [image: twitter icon] >>>>> <https://twitter.com/ciniter_ltd> [image: youtube icon] >>>>> <https://www.youtube.com/channel/UCfOgsIgX3l1TT4G79NBUt-A> [image: >>>>> linkedin icon] <https://www.linkedin.com/company/ciniter> >>>>> >>>>> >>>>> 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 >>>> the sender by reply e-mail. Any unauthorised use or dissemination of >>>> this message in any manner whatsoever, in whole or in part, is strictly >>>> prohibited. This e-mail, including all attachments hereto, (i) is for >>>> discussion purposes only and shall not be deemed or construed to be a >>>> professional opinion unless expressly stated otherwise, and (ii) is not >>>> intended, written or sent to be used, and cannot and shall not be used, for >>>> any unlawful purpose. This communication, including any attachments, may >>>> not be free of viruses, interceptions or interference, and may not be >>>> compatible with your systems. You should carry out your own virus checks >>>> before opening any attachment to this e-mail. The sender of this e-mail and >>>> *Fynarfin Tech Private Limited* shall not be liable for any damage >>>> that you may sustain as a result of viruses, incompleteness of this >>>> message, a delay in receipt of this message or computer problems >>>> experienced. >>>> >>>
