Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Once backup is completed (rear mkbackup), customer would like to log message that "backup complete" with a timestamp and location of the backup so the result can be inserted into a database.
Version-Release number of selected component (if applicable):
rear-1.17.2-1.el7.noarch
How reproducible:
Always
Steps to Reproduce:
Currently there is no provision to log message after successful backup completion.
Actual results:
Currently there is no provision to log message after successful backup completion.
Expected results:
Have some kind of provision to log message after successful backup completion only.
Additional info:
As a temporary hack, I modified /usr/sbin/rear bash script itself to log such message.
# Check for and run the requested workflow
if has_binary WORKFLOW_$WORKFLOW; then
Log "Running $WORKFLOW workflow"
WORKFLOW_$WORKFLOW "${ARGS[@]}"
Log "Finished running $WORKFLOW workflow $BACKUP_URL"
LogPrint "Finished running $WORKFLOW workflow $BACKUP_URL `date` " <<<<<< Added this line to print any messages and access variables
else
VERBOSE=1
LogPrint "ERROR: The specified command '$WORKFLOW' does not exist !"
EXIT_CODE=1
fi
I have not completely tested above but looks possible to get notification from here.
(In reply to Petr Hracek from comment #3)
> I would prefer to create a Pull Request to upstream.
> Relevant issue for it is: https://github.com/rear/rear/issues/1023
> Relevant upstream Pull Request: https://github.com/rear/rear/pull/1022
>
> We will see whether upstream accept it.
Thanks. hopefully it will get merge upstream and then downstream a well.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2052
Description of problem: Once backup is completed (rear mkbackup), customer would like to log message that "backup complete" with a timestamp and location of the backup so the result can be inserted into a database. Version-Release number of selected component (if applicable): rear-1.17.2-1.el7.noarch How reproducible: Always Steps to Reproduce: Currently there is no provision to log message after successful backup completion. Actual results: Currently there is no provision to log message after successful backup completion. Expected results: Have some kind of provision to log message after successful backup completion only. Additional info: As a temporary hack, I modified /usr/sbin/rear bash script itself to log such message. # Check for and run the requested workflow if has_binary WORKFLOW_$WORKFLOW; then Log "Running $WORKFLOW workflow" WORKFLOW_$WORKFLOW "${ARGS[@]}" Log "Finished running $WORKFLOW workflow $BACKUP_URL" LogPrint "Finished running $WORKFLOW workflow $BACKUP_URL `date` " <<<<<< Added this line to print any messages and access variables else VERBOSE=1 LogPrint "ERROR: The specified command '$WORKFLOW' does not exist !" EXIT_CODE=1 fi I have not completely tested above but looks possible to get notification from here.