[mariadb] multiple template key in backup-cronjob.yaml

Describe the bug

The MariaDB package fails to install when backup is enabled

Environment

v1.2.0
Provider: on-prem

To Reproduce
Steps to reproduce the behavior:

Go to a Tenant dashboard
Create a Managed MariaDB service
Set backup enabled
Submit

Expected behaviour
The HelmRelease install is successful

Actual behaviour
The HelpRelease fails to install

Logs

Helm install failed for release tenant-example/mariadb-example with chart [email protected]+5c35e21515d9: error while running post render on files: map[string]interface {}(nil): yaml: unmarshal errors: line 17: mapping key "template" already defined at line 14

cozystack/packages/apps/mariadb/templates/backup-cronjob.yaml

Lines 16 to 27 in 5da23f4

    
           template: 
        
             spec: 
        
               restartPolicy: OnFailure 
        
           template: 
        
             metadata: 
        
               annotations: 
        
                 checksum/config: {{ include (print $.Template.BasePath "/backup-script.yaml") . | sha256sum }} 
        
                 checksum/secret: {{ include (print $.Template.BasePath "/backup-secret.yaml") . | sha256sum }} 
        
             spec: 
        
               imagePullSecrets: 
        
               - name: {{ .Release.Name }}-regsecret 
        
               restartPolicy: Never

I'd create a PR, but I'm unsure which restartPolicy should be used

Checklist

I have checked the documentation
I have searched for similar issues
I have included all required information
I have provided clear steps to reproduce
I have included relevant logs

Jonathan Haines (@BarryThePenguin)

Hi Jonathan Haines (@BarryThePenguin)! I'm Dosu and I’m helping the cozystack team.

Thanks for the detailed report! This is a known issue — there's a duplicate template key in packages/apps/mariadb/templates/backup-cronjob.yaml at lines 14-17 .

PR #2279 has the fix for this, but it hasn't been merged yet. Until then, you'll need to either manually patch the template or deploy MariaDB without backup enabled.

This same bug pattern also affects PostgreSQL (#869) [1].

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

fix(clickhouse): remove duplicate template key and use correct cluste…

Verified against current main: this is already fixed. The duplicate template: key was removed in commit d2030be (fix(mariadb): always enable replication for consistent service naming, 2026-03-27) — two days before this issue was filed, so the report was against an older version. Current packages/apps/mariadb/templates/backup-cronjob.yaml has only one template: block at line 16. Marking triage/not-reproducible; safe to close once confirmed.

Closing as not reproducible — fix landed in d2030be before this report was filed (see prior comment for details).

[Backport release-1.2] fix(mariadb): remove duplicate template key in…

Navigation Menu

Repository navigation

[mariadb] multiple `template` key in `backup-cronjob.yaml` #2293

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	template:
	spec:
	restartPolicy: OnFailure
	template:
	metadata:
	annotations:
	checksum/config: {{ include (print $.Template.BasePath "/backup-script.yaml") . \| sha256sum }}
	checksum/secret: {{ include (print $.Template.BasePath "/backup-secret.yaml") . \| sha256sum }}
	spec:
	imagePullSecrets:
	- name: {{ .Release.Name }}-regsecret
	restartPolicy: Never

[mariadb] multiple template key in backup-cronjob.yaml #2293

Description

Activity

dosubot commented on Mar 29, 2026

lexfrei commented on Apr 27, 2026

lexfrei commented on Apr 27, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

[mariadb] multiple `template` key in `backup-cronjob.yaml` #2293