ScyllaCluster upgrades should deploy and update [It] with 3 member(s) and 1 rack(s) from 6.0.0 to 6.0.1

[rzetelskik]

Link to the job that flaked.

https://prow.scylla-operator.scylladb.com/view/gs/scylla-operator-prow/pr-logs/pull/scylladb_scylla-operator/2064/pull-scylla-operator-master-e2e-gke-parallel-clusterip/1823405236555878400#1:test-build-log.txt%3A2346

Snippet of what failed.

  [FAILED] Unexpected error:
      <*fmt.wrapError | 0xc0005301a0>: 
      waiting has been interupted ([false]): timed out waiting for the condition
      {
          msg: "waiting has been interupted ([false]): timed out waiting for the condition",
          err: <wait.errInterrupted>{
              cause: <*errors.errorString | 0xc0008f1b10>{
                  s: "timed out waiting for the condition",
              },
          },
      }
  occurred
  In [It] at: github.com/scylladb/scylla-operator/test/e2e/set/scyllacluster/scyllacluster_upgrades.go:62 @ 08/13/24 17:40:56.684
  Full Stack Trace
    github.com/scylladb/scylla-operator/test/e2e/set/scyllacluster.init.func18.2(0xc00066bce0)
    	github.com/scylladb/scylla-operator/test/e2e/set/scyllacluster/scyllacluster_upgrades.go:62 +0x72a
    reflect.Value.call({0x25eb840?, 0xc0004eef60?, 0x13?}, {0x2d33cfa, 0x4}, {0xc000a0aa68, 0x1, 0x1?})
    	reflect/value.go:596 +0xca6
    reflect.Value.Call({0x25eb840?, 0xc0004eef60?, 0x35b1790?}, {0xc000a0aa68?, 0x0?, 0x0?})
    	reflect/value.go:380 +0xb9

[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