Add more logging for missing processes in upgrade variations

[johscheuer]

Description

Add more logging for missing processes in upgrade variations.

Type of change

Please select one of the options below.

• Other

Discussion

Those additional logs hopefully help to better debug some of the failures during the upgrade variations.

Testing

CI will run e2e tests.

Documentation

-

Follow-up

-

[foundationdb-ci]

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

• Commit ID: 33caf481276e061b860346a7c00ad69a68664ee3
• Duration 2:55:02
• 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: 33caf48
• Duration 2:55:02
• 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.57 to 7.3.33 [e2e, pr]
  /codebuild/output/src3439532043/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/fixtures/ha_fdb_cluster.go:314

Ran 7 of 9 Specs in 6041.280 seconds
FAIL! -- 6 Passed | 1 Failed | 2 Pending | 0 Skipped
--- FAIL: TestOperatorHaUpgrade (6217.99s)
FAIL
FAIL    github.com/FoundationDB/fdb-kubernetes-operator/e2e/test_operator_ha_upgrades   6218.083s
FAIL

That is unrelated. I'm going to create an issue to look at it, I've seen this test fail sometimes.