Unable to initialize database tables: unable to open database file: out of memory - persistent volume attached to metricsScraper

[rubber-ant]

What happened?

│ I1112 15:36:28.587847       1 main.go:43] "Starting Metrics Scraper" version="1.2.1"                                                                                                  │
│ W1112 15:36:28.587961       1 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.                                │
│ I1112 15:36:28.588173       1 main.go:51] Kubernetes host: https://10.96.0.1:443                                                                                                      │
│ I1112 15:36:28.588181       1 main.go:52] Namespace(s): []                                                                                                                            │
│ F1112 15:36:28.588834       1 main.go:70] Unable to initialize database tables: unable to open database file: out of memory (14)                                                      │
│ Stream closed EOF for kubernetes-dashboard/kubernetes-dashboard-metrics-scraper-7c97bc8d64-wz254 (kubernetes-dashboard-metrics-scraper)

What did you expect to happen?

Volume mounted to metricScraper

How can we reproduce it (as minimally and precisely as possible)?

pvc.yaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: my-pvc
  namespace: kubernetes-dashboard
  annotations:
    volume.beta.kubernetes.io/storage-provisioner: rook-ceph.rbd.csi.ceph.com
    volume.kubernetes.io/storage-provisioner: rook-ceph.rbd.csi.ceph.com
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 100Gi
  storageClassName: xfs

helm

    values:
      - metricsScraper:
          containers:
            args:
              - --v=0
              - --db-file=/mnt/metrics.db
            volumeMounts:
                - mountPath: /mnt
                  name: scraper-pv-storage
          volumes:
            - name: scraper-pv-storage
              persistentVolumeClaim:
                claimName: my-pvc

pv and pvc

kubectl  get pv,pvc -A | grep dashboard
persistentvolume/pvc-d837a84b-2d16-4b2b-a2d1-54d28c93fb82   100Gi      RWO            Retain           Bound    kubernetes-dashboard/my-pvc       xfs            <unset>                          4m52s
kubernetes-dashboard   persistentvolumeclaim/my-pvc                    Bound    pvc-d837a84b-2d16-4b2b-a2d1-54d28c93fb82   100Gi      RWO            xfs            <unset>                 12m

Anything else we need to know?

backend using ceph - using the same storageclass for other sts without any issue

Ref: #5537

What browsers are you seeing the problem on?

No response

Kubernetes Dashboard version

7.9.0

Kubernetes version

1.29.10

Dev environment

No response

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.