Bug 40297

Summary: No active MariaDB 10.3 job even though we advertise it's support
Product: Project Infrastructure Reporter: Victor Grousset/tuxayo <victor>
Component: Continuous IntegrationAssignee: Tomás Cohen Arazi (tcohen) <tomascohen>
Status: Needs Signoff --- QA Contact:
Severity: critical    
Priority: P5 - low CC: tomascohen
Version: unspecified   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40295
GIT URL: Change sponsored?: ---
Patch complexity: --- Documentation contact:
Documentation submission: Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Victor Grousset/tuxayo 2025-07-02 17:06:01 UTC
bug 40295 implemented would have prevented Bug 40292.

But there is a larger problem of CI not in sync with https://wiki.koha-community.org/wiki/System_requirements_and_recommendations.

There might be other hidden v10.3 issues that need to have the core test suite be ran. The sys req wiki page says CI runs against all advertised versions. It might not be worth the massive resources to really honor that phrasing. Which could be relaxed. But ensuring the DB job is ran on the lowest DBMS is worth it. (that's Bug 40295) Maybe not for each stable release. And having the core suite also run for for the lowest DBMS should be worth it too. That's this ticket.
Comment 1 Tomás Cohen Arazi (tcohen) 2025-07-02 19:02:20 UTC
For reference:

Debian 11 -> MariaDB 10.5 (10.11 supported)
Debian 12 -> MariaDB 10.11 (11 available)
Ubuntu 22.04 -> MariaDB 10.06
Ubuntu 24.04 -> MariaDB 10.11

We could have a 10.3 task, but what do you think of our supported OS not providing support for it?
Comment 2 Tomás Cohen Arazi (tcohen) 2025-07-02 20:44:29 UTC
(In reply to Victor Grousset/tuxayo from comment #0)
> bug 40295 implemented would have prevented Bug 40292.
> 
> But there is a larger problem of CI not in sync with
> https://wiki.koha-community.org/wiki/System_requirements_and_recommendations.

We need to review those requirements. I rely on RMaints to let me know which tasks they need added, I can do it timely if requested.

Does this report imply adding this?

* main + MariaDB 10.3
* 25.05 + MariaDB 10.3

Which OS should we use? MariaDB runs on a separate container so we don't need the backend to support that specific version. There are some hardcoded MariaDB versions though:

https://gitlab.com/koha-community/koha-testing-docker/-/blob/main/jenkins_config/build.pl?ref_type=heads#L49
Comment 3 Tomás Cohen Arazi (tcohen) 2025-07-03 13:02:19 UTC
I've just patched KTD so we have more flexibility [1] and created a task for main+10.3 [2] to test if my patch does the job.

It does.

Please confirm which Koha versions you want to test with MariaDB 10.3

Thanks

[1] https://gitlab.com/koha-community/koha-testing-docker/-/commit/11fe925b4afa4d635007be38ad914b462554298f
[2] https://jenkins.koha-community.org/job/Koha_Main_MDB_10.3/1/console
Comment 4 Victor Grousset/tuxayo 2025-07-04 05:55:09 UTC
(In reply to Tomás Cohen Arazi (tcohen) from comment #1)
> We could have a 10.3 task, but what do you think of our supported OS not
> providing support for it?

It's advertised so even if it's a mistake, it makes sense to still have it for the end of the cycle. It seems in the last dev meeting, the scale tilted in favor of not dropping 10.3, which was a proposed solution to that RENAME COLUMN issue.

22.11 LTS still advertises Ubuntu 20.04 which ships with MariaDB 10.3 by default IIUC.

And Ubuntu 20.04 is only EOL since a month.

MariaDB 10.3 is EOL since 2 years so unless we hear enough about explicit usage it won't make sense to keep it around next cycle. (IMHO)
The person that hit the RENAME COLUMN issue didn't realize their Debian 10 is EOL since a year. And they will upgrade it.


-------


(In reply to Tomás Cohen Arazi (tcohen) from comment #2)
> (In reply to Victor Grousset/tuxayo from comment #0)
> We need to review those requirements. I rely on RMaints to let me know which
> tasks they need added

+1, because on a new cycle, we can easily forget stuff that is way past EOL.
It's very possible that we wouldn't have advertised MariaDB 10.3 for 25.05.
I'm not sure where in our processes it would be a good place to refresh the requirements.

-----

> Does this report imply adding this?
> 
> * main + MariaDB 10.3
> * 25.05 + MariaDB 10.3

Maybe I'm wrong but it doesn't look likely that we will support MariaDB 10.3 for 25.11.
So what about just 25.05?
So there is a decent safeguard for MariaDB 10.3 without spending too much setup time and runner resources for that 2 years old EOL DBMS.
Not sure adding jobs for 24.11, 24.05, 22.11 has a meaningful chance of catching a bug that the 25.05 job wouldn't.

------

(In reply to Tomás Cohen Arazi (tcohen) from comment #3)
> I've just patched KTD so we have more flexibility [1] and created a task for
> main+10.3 [2] to test if my patch does the job.

Cool, thanks! :D These mariadb_d11, etc images are a bit confusing so being able to add directly a MariaDB version is more simple.
Comment 5 Victor Grousset/tuxayo 2025-07-04 06:02:15 UTC
> Does this report imply adding this?

I don't remember why I though main and stable. But I certainly wasn't aware that MariaDB 10.3 was totally EOL ^^"