Bug #108526 Innodbcluster add backup doesn't always take affect
Submitted: 16 Sep 2022 13:56 Modified: 29 Sep 2022 16:03
Reporter: Ales Verbic (OCA) Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Operator Severity:S2 (Serious)
Version: OS:Any
Assigned to: MySQL Verification Team CPU Architecture:Any
Tags: 8.0.30:2.0.5

[16 Sep 2022 13:56] Ales Verbic 
Description:
Update to InnoDBCluster resource to add backup doesn't always take effect without restarting the operator.

How to repeat:
Hard to reproduce it.

I was playing with backup parameters and upgrading the helm chart for innodbcluster until I realized the cronjob was not created.
[22 Sep 2022 23:02] MySQL Verification Team 
Hi,

Thank you for your report but I need more data as I cannot reproduce this myself. Do you have logs from the time you did reproduce it?

thanks
[27 Sep 2022 13:45] Ales Verbic 
I don't have the steps to reproduce it.

It happened to me. When I was running helm upgrade and adding different values to see if backup works and what parameters get applied. Turning on and off backups. The operator "froze" and stopped responding to future upgrade changes that appeared in the innodbcluster resource. After the restart of the operator. Things started working again.
[29 Sep 2022 16:03] MySQL Verification Team 
Hi,

I cannot reproduce that behavior but I passed the info to the operator team.