Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

helm template for post install bucket hook is failing after #5081 was merged. error: no template "master.hostpath_exists" associated with template "gotpl" #5107

Closed
jessebot opened this issue Dec 14, 2023 · 0 comments · Fixed by #5108

Comments

@jessebot
Copy link
Contributor

jessebot commented Dec 14, 2023

Describe the bug

When #5081 removed master.hostpath_exists and master.existing_claims, it wasn't removed from here:

{{- $hostpath_exists := include "master.hostpath_exists" . -}}
{{- $existing_claims := include "master.existing_claims" . -}}

however, it doesn't seem to be doing anything anyway...

$ helm template . --name-template nextcloud-seaweedfs --namespace nextcloud --kube-version 1.27 --values /tmp/4639d6f4-1a20-47a5-9e35-288c9bf1584c --include-crds
Error: template: seaweedfs/templates/post-install-bucket-hook.yaml:84:28: 
executing "seaweedfs/templates/post-install-bucket-hook.yaml" at <include "master.hostpath_exists" .>: 
error calling include: template: no template "master.hostpath_exists" associated with template "gotpl" 
Use --debug flag to render out invalid YAML

System Setup
This is the helm chart, so I'm running k3s, and then I'm using Argo CD to deploy this chart.

The values I'm using in my Seaweedfs Argo CD ApplicationSet for nextcloud to reproduce this error:

filer:
  # this enables the filer and s3 which are both required to be deployed together
  s3:
    enabled: true
    allowEmptyFolder: false
    domainName: 's3.example.com'
    # enable user & permission to s3 (need to inject to all services)
    enableAuth: true
    existingConfigSecret: seaweedfs-s3-secret
    createBuckets:
      - name: nextcloud-data
        anonymousRead: false
      - name: nextcloud-postgres
        anonymousRead: false

Expected behavior
I'd expect the above to work as normal and deploy the post install hook for the bucket creation.

Additional context

Can submit a PR to fix this. If I do, please merge this one first: #5106 so we can make sure it's working in this repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant