[Flake] CSI upstream local.csi.scylladb.com [Testpattern: Dynamic PV (default fs)] capacity [It] provides storage capacity information

[rzetelskik]

  STEP: Creating a kubernetes client @ 01/03/25 10:57:08.586
  Jan  3 10:57:08.586: INFO: >>> kubeConfig: /tmp/kubeconfig-2232190345
  STEP: Building a namespace api object, basename capacity @ 01/03/25 10:57:08.587
  STEP: Waiting for a default service account to be provisioned in namespace @ 01/03/25 10:57:09.063
  STEP: Waiting for kube-root-ca.crt to be provisioned in namespace @ 01/03/25 10:57:09.083
  STEP: Creating a StorageClass @ 01/03/25 10:57:09.128
  [FAILED] in [It] - k8s.io/[email protected]/test/e2e/storage/testsuites/capacity.go:135 @ 01/03/25 10:58:09.155
  Jan  3 10:58:09.156: INFO: deleting storage class local-csi-sc-zwrdn
  STEP: Destroying namespace "capacity-2156" for this suite. @ 01/03/25 10:58:09.174
  << Timeline
  [FAILED] Timed out after 60.000s.
  after creating storage class
  no CSIStorageCapacity objects for storage class "local-csi-sc-zwrdn"

https://prow.scylla-operator.scylladb.com/view/gs/scylla-operator-prow/pr-logs/pull/scylladb_local-csi-driver/72/pull-local-csi-driver-master-e2e-gke-parallel/1875131340463017984#1:test-build-log.txt%3A3131

/kind flake
/priority important-longterm

[scylla-operator-bot]

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

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

• After 30d 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

/lifecycle stale

[scylla-operator-bot]

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

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

• After 30d 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

/lifecycle rotten