K8 spg 604 update restart

[eleo007]

CHANGE DESCRIPTION

Problem:
The update-minor tests does not detect that pg cluster objects are restarted during operator update

Cause:
Update of cr starts at once after the operator.

Solution:
Add sleep and sts/deploy/pg generations check after operator update.

CHECKLIST

Jira

• Is the Jira ticket created and referenced properly?
• Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
• Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

• Is an E2E test/test case added for the new feature/change?
• Are unit tests added where appropriate?

Config/Logging/Testability

• Are all needed new/changed options added to default YAML files?
• Did we add proper logging messages for operator actions?
• Did we ensure compatibility with the previous version or cluster upgrade process?
• Does the change support oldest and newest supported PG version?
• Does the change support oldest and newest supported Kubernetes version?

[JNKPercona]

Test name	Status
custom-extensions	passed
custom-tls	passed
demand-backup	failure
finalizers	passed
init-deploy	passed
major-upgrade	failure
monitoring	passed
one-pod	passed
operator-self-healing	failure
pitr	passed
scaling	passed
scheduled-backup	passed
self-healing	passed
start-from-backup	passed
tablespaces	passed
telemetry-transfer	passed
upgrade-consistency	passed
upgrade-minor	failure
users	passed
We run 19 out of 19

commit: 483b7cd
image: perconalab/percona-postgresql-operator:PR-915-483b7cd40