Add test case to validate that the upgrade is stuck when the new binary is missing

[johscheuer]

Description

This test makes sure that our upgrade is stuck when the new binary is missing from one of the Pods.

Type of change

• Other

Discussion

Testing

Ran the test manually:

2023/03/29 07:44:44 storage-2 IncorrectCommandLine
2023/03/29 07:45:13 finished all tests, start deleting namespace jscheuermann-xtfzxidt
• [288.991 seconds]
------------------------------
[AfterSuite]
/Users/jscheuermann/go/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/test_operator_upgrades/operator_upgrades_test.go:53
[AfterSuite] PASSED [0.000 seconds]
------------------------------
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
[ReportAfterSuite] PASSED [0.004 seconds]
------------------------------

Ran 1 of 12 Specs in 288.991 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 11 Skipped
PASS | FOCUSED
FAIL    github.com/FoundationDB/fdb-kubernetes-operator/e2e/test_operator_upgrades      289.387s

Documentation

Added documentation in the test code.

Follow-up

[foundationdb-ci]

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

• Commit ID: 55bebea
• Duration 2:39:21
• 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)