K8SPSMDB-934: add more logs to mongodb-healthcheck

[pooknull]

https://perconadev.atlassian.net/browse/K8SPSMDB-934

DESCRIPTION

This pull request removes a lot of unused code for mongodb-healthcheck.

It also introduces several logging improvements:

• more log messages
• setting the default log level to DEBUG
• storing logs in /data/db/mongod-data/logs/mongodb-healthcheck.log file

Additionally, each time the healthcheck fails, the current log is saved to the gzip compressed file mongodb-healthcheck-<timestamp>.log.gz and the file mongodb-healthcheck.log is reset. Logs older than 24 hours will be deleted.

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?
• Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

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 MongoDB version?
• Does the change support oldest and newest supported Kubernetes version?

[egegunes]

why?

[pooknull]

For some reason, the pvc-resize test kept failing in this PR.

There was a case where statefulset had an updated resources (configured var), but pvcs didn't (actual var). In this case it was not possible to start a resize because requested.Cmp(configured) == 0 was true while requested.Cmp(actual) == 0 wasn't.

[pooknull]

e95cda3

[inelpandzic]

Could we set this through some env var? What if a user doesn't want this level of verbosity?

I think this should be configurable. Maybe we don't need to have it now, but maybe a task to have it. Log levels generally should be configurable, especially if we set it to a more verbose level and you can't change it.

[pooknull]

c9efc0c

[JNKPercona]

Test name	Status
arbiter	passed
balancer	passed
custom-replset-name	passed
custom-tls	passed
cross-site-sharded	passed
data-at-rest-encryption	passed
data-sharded	passed
demand-backup	passed
demand-backup-eks-credentials	passed
demand-backup-physical	passed
demand-backup-physical-sharded	passed
demand-backup-sharded	passed
expose-sharded	passed
ignore-labels-annotations	passed
init-deploy	passed
finalizer	passed
ldap	passed
ldap-tls	passed
limits	passed
liveness	passed
mongod-major-upgrade	passed
mongod-major-upgrade-sharded	passed
monitoring-2-0	passed
multi-cluster-service	passed
non-voting	passed
one-pod	passed
operator-self-healing-chaos	passed
pitr	passed
pitr-sharded	passed
pitr-physical	passed
pvc-resize	passed
recover-no-primary	passed
rs-shard-migration	passed
scaling	passed
scheduled-backup	passed
security-context	passed
self-healing-chaos	passed
service-per-pod	passed
serviceless-external-nodes	passed
smart-update	passed
split-horizon	passed
storage	passed
tls-issue-cert-manager	passed
upgrade	passed
upgrade-consistency	passed
upgrade-consistency-sharded-tls	passed
upgrade-sharded	passed
users	passed
version-service	passed
We run 49 out of 49

commit: 1c5a404
image: perconalab/percona-server-mongodb-operator:PR-1587-1c5a4043