Improve the tester handling when a cluster is upgraded

[johscheuer]

Description

A cluster that contains tester processes can block the upgrade. The changes in this PR will change this and ignore tester processes in the pending upgrade check as those processes are reporting to the cluster but cannot be restarted with fdbcli.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Discussion

I added a new e2e test for this setup.

Testing

Ran the test manually.

Documentation

-

Follow-up

-

[foundationdb-ci]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: 4cf542dc2bdd0806f8f84b5d265da29e11e17dbe
• Duration 2:59:27
• Result: :x: FAILED
• Error: Error while executing command: if $fail_test; then exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: 8659e33bc8fbd539e194d0e9dcc5d9cee150359b
• Duration 2:58:22
• Result: :white_check_mark: SUCCEEDED
• Error: N/A
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: 973e6ae0e1320683601bff885f227a8c81f47aef
• Duration 2:56:55
• Result: :x: FAILED
• Error: Error while executing command: if $fail_test; then exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: 973e6ae0e1320683601bff885f227a8c81f47aef
• Duration 3:02:46
• Result: :x: FAILED
• Error: Error while executing command: if $fail_test; then exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: 973e6ae0e1320683601bff885f227a8c81f47aef
• Duration 3:17:57
• Result: :x: FAILED
• Error: Error while executing command: if $fail_test; then exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: 973e6ae0e1320683601bff885f227a8c81f47aef
• Duration 3:02:09
• Result: :x: FAILED
• Error: Error while executing command: if $fail_test; then exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: 973e6ae0e1320683601bff885f227a8c81f47aef
• Duration 2:43:53
• Result: :x: FAILED
• Error: Error while executing command: if $fail_test; then exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[johscheuer]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: 973e6ae
• Duration 2:43:53
• Result: ❌ FAILED
• Error: Error while executing command: if $fail_test; then exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

Summarizing 1 Failure:
  [FAIL] Operator HA Upgrades when no remote storage processes are restarted [It] Upgrade from 7.1.63 to 7.3.43 [e2e, pr]
  /codebuild/output/src714216153/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/fixtures/ha_fdb_cluster.go:314

Ran 8 of 10 Specs in 5763.040 seconds
FAIL! -- 7 Passed | 1 Failed | 2 Pending | 0 Skipped
--- FAIL: TestOperatorHaUpgrade (5851.08s)
FAIL
FAIL    github.com/FoundationDB/fdb-kubernetes-operator/e2e/test_operator_ha_upgrades   5851.102s
FAIL

That's another test that failed. I'll spend some time next week looking into the test stability.