cleared disks of controller-0 and reinstall.
make controller-0 as the active controller (controller-1 was the active controller)
deleted and added stx-openstack  but still failing the same pod.

https://paste.opendev.org/show/808170/

On Tue, Aug 17, 2021 at 6:30 PM open infra <openinfradn@gmail.com> wrote:
Hi Douglas,

Both pods have similar disk usage and 4.4GB remaining space out of 4.8GB in /var/lib/mysql directory.
https://paste.opendev.org/show/808142/

I have allocated 200GB for docker-lv
Regards,
Danishka

On Tue, Aug 17, 2021 at 5:38 PM Douglas Lopes Pereira <douglas.pereira@windriver.com> wrote:
Hi Danishka,

can you confirm there is enough disk space in your controller for the MariaDB pod to recover?

Regards,
Doug

On Tue, Aug 17, 2021 at 8:25 AM open infra <openinfradn@gmail.com> wrote:

[Please note: This e-mail is from an EXTERNAL e-mail address]


In the logs of the pod (mariadb-server-1) [4], I noticed issues related to mariadb tables but only in the failed pod.
This pod keeps rebooting and also stx-openstack applying keep fails each time.

2021-08-17 00:19:12,237 - OpenStack-Helm Mariadb - INFO - Recovering wsrep position: 2021-08-17  0:19:10 140357388367552 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2021-08-17 00:19:12,237 - OpenStack-Helm Mariadb - INFO - Recovering wsrep position: 2021-08-17  0:19:10 140357388367552 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
 
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss