[Bug 29378] New: After the automatic update to 21.05.05, the OPAC switches to maintenance mode and the web installer is displayed
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 Bug ID: 29378 Summary: After the automatic update to 21.05.05, the OPAC switches to maintenance mode and the web installer is displayed Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs@lists.koha-community.org Reporter: resetka.bedi@gmail.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com I wanted to log in to the Staff interface after the automatic update on 21.05.05 but I saw Welcome to the Koha 21.05 web installer. So I logged in with the data I found in the koha-conf.xml configuration file. After a few steps, I updated the database from version 21.05.04.003 to 21.05.05.000. It wrote that the operation was successful and I was able to continue to the login page. Unfortunately, I got back to the Check Perl dependencies installation wizard. URL structure is: http://staff-library.sample.com/cgi-bin/koha/installer/install.pl?step=1&op=updatestructure -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|enhancement |blocker CC| |kyle@bywatersolutions.com --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hi Pavel, there is actually a small mistake in the version that is causing this that will be fixed as soon as possible. Do you have access to your database with SQL? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 --- Comment #2 from Pavel Bédi <resetka.bedi@gmail.com> --- (In reply to Katrin Fischer from comment #1)
Hi Pavel, there is actually a small mistake in the version that is causing this that will be fixed as soon as possible. Do you have access to your database with SQL?
Yes, I have. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 --- Comment #3 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Ok, the problem is that the version in Koha.pm doesn't match the one in the database because of a forgotten database update. When they both match again, you will get out of the installer loop. Koha.pm has: $VERSION = "21.05.05.000"; So this should do the trick: UPDATE systempreferences SET value = "21.0505000" where variable = "Version"; You might need to restart Plack/Memcached for Koha to take notice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 Pavel Bédi <resetka.bedi@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |LATER -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|LATER |--- --- Comment #4 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Did it work alright? Leaving this open as we still need to fix it in Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 --- Comment #5 from Pavel Bédi <resetka.bedi@gmail.com> --- (In reply to Katrin Fischer from comment #4)
Did it work alright? Leaving this open as we still need to fix it in Koha.
Yes, thank you very much! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 Mason James <mtj@kohaaloha.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mtj@kohaaloha.com --- Comment #6 from Mason James <mtj@kohaaloha.com> --- (In reply to Katrin Fischer from comment #4)
Did it work alright? Leaving this open as we still need to fix it in Koha.
i've pushed a new 21.05.05-2 package, with the database update added -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 Mason James <mtj@kohaaloha.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |Needs Signoff -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 --- Comment #7 from Mason James <mtj@kohaaloha.com> --- Created attachment 127123 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=127123&action=edit DBRev 21.05.05.002 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 --- Comment #8 from Mason James <mtj@kohaaloha.com> --- hi Kyle, i've attached a patch, to be added to the 21.05 branch -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 Victor Grousset/tuxayo <victor@tuxayo.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |victor@tuxayo.net --- Comment #9 from Victor Grousset/tuxayo <victor@tuxayo.net> --- $DBversion = '21.05.05.002'; Minor mistake in the patch. The 4th part should be zeroed when incrementing the 3rd part for a release. Example from a past release: https://git.koha-community.org/Koha-community/Koha/commit/b17cf65633107306bd... This means the version in DB > version in code: https://git.koha-community.org/Koha-community/Koha/commit/ba30e76d1a08ef84e6... I don't think that should cause issues (though I don't know eventual quirks of version management). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 --- Comment #10 from Victor Grousset/tuxayo <victor@tuxayo.net> --- (but it's important for Kyle and Nick to account for that and not fix it by starting from 21.05.05.000 because it's been distributed and ran already) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 Mason James <mtj@kohaaloha.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #127123|0 |1 is obsolete| | --- Comment #11 from Mason James <mtj@kohaaloha.com> --- Created attachment 127125 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=127125&action=edit DBRev 21.05.05.003 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 --- Comment #12 from Mason James <mtj@kohaaloha.com> --- (In reply to Victor Grousset/tuxayo from comment #10)
(but it's important for Kyle and Nick to account for that and not fix it by starting from 21.05.05.000 because it's been distributed and ran already)
i've released a package as 21.05.05.003, so here's the patch for that -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 --- Comment #13 from Mason James <mtj@kohaaloha.com> --- (In reply to Mason James from comment #12)
(In reply to Victor Grousset/tuxayo from comment #10)
(but it's important for Kyle and Nick to account for that and not fix it by starting from 21.05.05.000 because it's been distributed and ran already)
i've released a package as 21.05.05.003, so here's the patch for that
root@deb10:/home/mason# apt-cache policy koha-common koha-common: Installed: 21.05.05-3 Candidate: 21.05.05-3 Version table: *** 21.05.05-3 500 500 http://debian.koha-community.org/koha stable/main amd64 Packages 100 /var/lib/dpkg/status -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 --- Comment #14 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Victor is right, that it should have been 21.05.05.000, because the 003 suggests 3 database updates in the cycle up to 21.05.05. It usually goes like this: 21.05.04.000 (release of 21.05.04) 21.05.04.001 (first database update for 21.05.05) 21.05.04.002 (second database update for 21.05.05 ... 21.05.05.000 (release of 21.05.05 - which was missing here) 21.05.05.001 (first database update for 21.05.06) ... I guess we could either set back to 21.05.05.000 at the beginning of the cycle now or Kyle will have to start 21.05.05.004 now. Just trying to explain the misunderstanding and why we need to deal with it now. As the packages are out there, it's too risky not to deal with the unexpected jump. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 --- Comment #15 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Katrin Fischer from comment #14)
Victor is right, that it should have been 21.05.05.000, because the 003 suggests 3 database updates in the cycle up to 21.05.05.
Argh. This should be: in the cylce up to 21.05.06! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 --- Comment #16 from Victor Grousset/tuxayo <victor@tuxayo.net> ---
I guess we could either set back to 21.05.05.000 at the beginning of the cycle now or Kyle will have to start 21.05.05.004 now.
The DB upgrade to 21.05.05.002 has already been released so we can't move it backwards right? So Kyle should just have to continue from 21.05.05.004 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 --- Comment #17 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Victor Grousset/tuxayo from comment #16)
I guess we could either set back to 21.05.05.000 at the beginning of the cycle now or Kyle will have to start 21.05.05.004 now.
The DB upgrade to 21.05.05.002 has already been released so we can't move it backwards right? So Kyle should just have to continue from 21.05.05.004
You are probably right about continuing with 21.05.05.004. Maybe there won't even be a database update this cycle so we can jump to 21.05.06.000 next. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 --- Comment #18 from Mason James <mtj@kohaaloha.com> --- (In reply to Katrin Fischer from comment #17)
(In reply to Victor Grousset/tuxayo from comment #16)
I guess we could either set back to 21.05.05.000 at the beginning of the cycle now or Kyle will have to start 21.05.05.004 now.
The DB upgrade to 21.05.05.002 has already been released so we can't move it backwards right? So Kyle should just have to continue from 21.05.05.004
You are probably right about continuing with 21.05.05.004. Maybe there won't even be a database update this cycle so we can jump to 21.05.06.000 next.
yes, i think Katrin is correct :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 Fridolin Somers <fridolin.somers@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fridolin.somers@biblibre.co | |m --- Comment #19 from Fridolin Somers <fridolin.somers@biblibre.com> --- I see this is actually in 21.05.x : https://git.koha-community.org/Koha-community/Koha/commit/1b39d0717a4b81cda2... And there is a DBRev 21.05.05.004 for Bug 29386 So problem solved ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29378 Mason James <mtj@kohaaloha.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |RESOLVED Resolution|--- |FIXED --- Comment #20 from Mason James <mtj@kohaaloha.com> --- (In reply to Fridolin Somers from comment #19)
I see this is actually in 21.05.x : https://git.koha-community.org/Koha-community/Koha/commit/ 1b39d0717a4b81cda28c72e07bb47e534d9d205b
And there is a DBRev 21.05.05.004 for Bug 29386
So problem solved ?
i think yes, we can close the bug -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org