Declarative schedule fails to run

[darnone]

What steps did you take and what happened:
I am deploying velero using helm chart and ArgoCD. When I deploy velero, create a schedule, and create a backup from the schedule the backup runs fine But if I define that same schedule declartivel using helm chart values, the schedule is create but backups from them do not work. I fact they are not created at all

What did you expect to happen:

The following information will help us better understand what's going on:

If you are using velero v1.7.0+:
I would add a bundle but the backup does not exist.

If you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)

• kubectl logs deployment/velero -n velero
• velero backup describe <backupname> or kubectl get backup/<backupname> -n velero -o yaml
• velero backup logs <backupname>
• velero restore describe <restorename> or kubectl get restore/<restorename> -n velero -o yaml
• velero restore logs <restorename>

Anything else you would like to add:

Environment:

• Velero version (use velero version): 1.15.2
• Velero features (use velero client config get features): features: but CSI Enabled is in my config
• Kubernetes version (use kubectl version): 1.30.9
• Kubernetes installer & version: 1.30.9
• Cloud provider or hardware configuration: AWS EKS
• OS (e.g. from /etc/os-release): Amazon Linux 2

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "I would like to see this bug fixed as soon as possible"
• 👎 for "There are more important bugs to focus on right now"

[darnone]

schedule config from helm chart:

schedules:
  gts-cicd-dev-schedule-fsb:
    disabled: false
    schedule: " 15 2 * * 1-5"
    template:
      csiSnapshotTimeout: 0s
      defaultVolumesToFsBackup: true
      ttl: "0s"
      excludedNamespaces:
      - velero
      - default
      hooks: {}
      includedNamespaces:
      - "*"
      includedResources:
      - "*"
      itemOperationTimeout: 0s
      metadata: {}
    useOwnerReferencesInBackup: false

[blackpiglet]

Could you help collect the debug bundle by running CLI velero debug and upload the generated tarball here?

[darnone]

I would provide a bundle but no backups are created:

"velero-gts-cicd-dev-schedule-fsb-20250310133750" not found

I can send a log:

schedule created from chart - config attached
velero backup create --from-schedule gts-cicd-ci-dev-schedule-fsb

no job.batch
velero backup create --from-schedule velero-gts-cicd-dev-schedule-fsb

INFO[0000] No Schedule.template.metadata.labels set - using Schedule.labels for backup object  backup=velero/velero-gts-cicd-dev-schedule-fsb-20250310151521 labels="map[app.kubernetes.io/instance:velero app.kubernetes.io/managed-by:Helm app.kubernetes.io/name:velero helm.sh/chart:velero-8.5.0]"
Creating backup from schedule, all other filters are ignored.
Backup request "velero-gts-cicd-dev-schedule-fsb-20250310151521" submitted successfully.
Run `velero backup describe velero-gts-cicd-dev-schedule-fsb-20250310151521` or `velero backup logs velero-gts-cicd-dev-schedule-fsb-20250310151521` for more details.

velero backup describe velero-gts-cicd-dev-schedule-fsb-20250310151521
An error occurred: backups.velero.io "velero-gts-cicd-dev-schedule-fsb-20250310151521" not found

kubectl logs -n velero velero-59d99f78d7-r8fvk > velero-lob.txt
Defaulted container "velero" out of: velero, velero-plugin-for-aws (init)

velero-log.yaml.zip

dev.yaml.zip

[darnone]

I see in the log:
time="2025-03-10T15:13:07Z" level=error msg="Current BackupStorageLocations available/unavailable/unknown: 0/0/1)" controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:181"

my configuration section:

configuration:
  features: EnableCSI
  uploaderType: kopia
  backupStorageLocation:
  - name: velero-backup-storage-location
    #bucket: {{ .Values.velero_backups_bucket }}
    bucket: gts-argocd-ci-velero-dev
    default: true
    provider: aws
    config:
      region: us-east-1
  volumeSnapshotLocation:
  - name: velero-volume-storage-location
    provider: aws
    config:
      region: us-east-1
  repositoryMaintenanceJob:
    requests:
      cpu: 1000m
      memory: 1024Mi
    limits:
      memory: 2048Mi

[darnone]

debug file

bundle-2025-03-10-11-30-21.tar.gz

[darnone]

Will this fix address fix my issue?

[blackpiglet]

Please check whether the ArgoCD prunes the generated backup.

[blackpiglet]

Will this fix address fix my issue?

No, I don't think that is related to this issue.