powerdns-release pod hangs with invalid option innodb-read-committed

[cvstebut]

Hi, when I tried deploying the chart, the admin app could not connect to the api. Finally I had a look powerdns-release pod logs. It showed something along the lines of invalid option innodb-read-committed. The powerdns docs have the name of the option as 'gmysql-innodb-read-commited'

After changing line 76 of powerdns-deployment.yaml to - name: PDNS_gmysql_innodb_read_committed, I was able to get a running system.

Any thoughts on how to proceed?

Thanks Christian

[vldanch]

@cvstebut After changing PDNS_gmysql_innodb_read_committed, the poverdns still did not work for me ...

what did you specifically do in order for everything to work properly?

[aescanero]

Update helm to 0.1.10 with "PDNS_gmysql_innodb_read_committed" Added new option powerdns.innodb_read_committed default 'no' Refs: https://doc.powerdns.com/authoritative/backends/generic-mysql.html#gmysql-innodb-read-committed https://dev.mysql.com/doc/refman/8.0/en/innodb-transaction-isolation-levels.html https://mariadb.com/kb/en/set-transaction/#:~:text=based%20binary%20logging.-,REPEATABLE%20READ,established%20by%20the%20first%20read.

@vldanch Could you post the logs here?