INTLY-3934 - add timestamp to scripts

[KevFan]

Description

Adds timestamps to the relevant echo logs to have a better idea on timing / duration when performing a backup

Jira

• https://issues.redhat.com/browse/INTLY-3934

Verification

• Provision integreatly workshop with OS3 installed
• Run the install_backup from the installation repo to install the backup cronjobs

ansible-playbook playbooks/install_backups.yml -e backup_s3_aws_access_key=<YOUR_S3_ACCESS_KEY> -e backup_s3_aws_secret_key=<YOUR_S3_SECRET_KEY> -e backup_s3_aws_bucket=<YOUR_S3_NAME> -e 'ns_prefix=' -e backup_image=quay.io/kevfan/backup-container:latest

• Scale down the ups operator to 0 to prevent it from reconciling back to hardcoded value

oc edit deployment unifiedpush-operator -n mobile-unifiedpush

• Edit the cronjob in the ups namespace to use quay.io/kevfan/backup-container:latest

oc edit cronjob ups-daily-at-midnight -n mobile-unifiedpush

• Scale down the sso operator to 0 to prevent it from reconciling back to hardcoded value

oc edit deployment keycloak-operator -n sso

• Edit the cronjob in the sso namespace to use quay.io/kevfan/backup-container:latest

 oc edit cronjob daily-at-midnight-sso -n sso

• Run the following backup jobs (taken from backup SOPs, ensuring the there is now some timestamps to the logs and finishes successfully uploading the backup without error

oc create job 3scale-mysql-backup-$(date +"%Y-%m-%d-%H%M%S") --from=cronjob/3scale-mysql-backup -n openshift-integreatly-backups
oc create job 3scale-postgres-backup-$(date +"%Y-%m-%d-%H%M%S") --from=cronjob/3scale-postgres-backup -n openshift-integreatly-backups
oc create job 3scale-redis-backup-$(date +"%Y-%m-%d-%H%M%S") --from=cronjob/3scale-redis-backup -n openshift-integreatly-backups
oc create job enmasse-postgres-backup-$(date +"%Y-%m-%d-%H%M%S") --from=cronjob/enmasse-postgres-backup -n openshift-integreatly-backups
oc create job enmasse-pv-backup-$(date +"%Y-%m-%d-%H%M%S") --from=cronjob/enmasse-pv-backup -n openshift-integreatly-backups
oc create job codeready-postgres-backup-$(date +"%Y-%m-%d-%H%M%S") --from=cronjob/codeready-postgres-backup -n openshift-integreatly-backups
oc create job codeready-pv-backup-$(date +"%Y-%m-%d-%H%M%S") --from=cronjob/codeready-pv-backup -n openshift-integreatly-backups
oc create job fuse-postgres-backup-$(date +"%Y-%m-%d-%H%M%S") --from=cronjob/fuse-postgres-backup -n openshift-integreatly-backups
oc create job launcher-postgres-backup-$(date +"%Y-%m-%d-%H%M%S") --from=cronjob/launcher-postgres-backup -n openshift-integreatly-backups
oc create job resources-backup-$(date +"%Y-%m-%d-%H%M%S") --from=cronjob/resources-backup -n openshift-integreatly-backups
oc create job ups-postgres-backup-$(date +"%Y-%m-%d-%H%M%S") --from=cronjob/ups-daily-at-midnight -n openshift-mobile-unifiedpush

[dimitraz]

Verified, the pod logs contain timestamps as expected.

Example logs from the launcher-postgres-backup job:

2020-01-21 12:13:55 ==> Upload /tmp/intly/archives/launcher.root-12_13_53.pg_dump.gz completed
2020-01-21 12:13:55 ==> [2020/01/21] Backup completed
2020-01-21 12:13:55 ==> Finished Backup

[jessesarn]

/lgtm
/approve