[Playbooks] - mariadb disabled #435

Closed
opened 2023-02-11 09:16:18 +01:00 by meaz · 2 comments
Owner

We need to review all settings and prepare to push bullseye and mariadb 10.5 before. It's safe to run the role on new containers or separate container (create staging playbook just for that container) but atm we shouldn't run playbook on the group of hosts as it is now.

We need to review all settings and prepare to push bullseye and mariadb 10.5 before. It's safe to run the role on new containers or separate container (create staging playbook just for that container) but atm we shouldn't run playbook on the group of hosts as it is now.
meaz added this to the 23.03 - March milestone 2023-02-25 08:45:34 +01:00
Author
Owner

Mariadb roles works fine with 10.5 version (tested on vagrant with roundcube role).

What do we have to do @muppeth ? Check my.cnf in each of the following containers and check if it matches what is set in container host_vars?

  • nextcloud DB
  • roundcube DB
  • akkaunting DB
  • zabbix_server
  • lacre
  • monitoring
Mariadb roles works fine with 10.5 version (tested on vagrant with roundcube role). What do we have to do @muppeth ? Check my.cnf in each of the following containers and check if it matches what is set in container host_vars? * nextcloud DB * roundcube DB * akkaunting DB * zabbix_server * lacre * monitoring
muppeth added this to the 23.03 - March project 2023-03-08 12:13:11 +01:00
muppeth self-assigned this 2023-03-16 21:36:15 +01:00
Owner

We can close this one. I have adjusted things when doing app migration to Ramashka.

We can close this one. I have adjusted things when doing app migration to Ramashka.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Disroot/Disroot-Project#435
No description provided.