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.
Bug 1377547 - Notification feature in rear
Summary: Notification feature in rear
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rear
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jakub Mazanek
QA Contact: Tereza Cerna
URL:
Whiteboard:
Depends On:
Blocks: 1298243 1393870 1400961
TreeView+ depends on / blocked
 
Reported: 2016-09-20 05:30 UTC by ajit mote
Modified: 2020-09-10 09:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-08-01 22:19:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2052 0 normal SHIPPED_LIVE rear bug fix update 2017-08-01 19:33:49 UTC

Description ajit mote 2016-09-20 05:30:49 UTC
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.

Comment 3 Petr Hracek 2016-10-04 08:41:45 UTC
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.

Comment 4 ajit mote 2016-10-04 08:52:16 UTC
(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.

Comment 10 Petr Hracek 2016-10-19 11:57:02 UTC
See upstream comments and feel free to comment it.
https://github.com/rear/rear/pull/1022

Comment 11 ajit mote 2016-10-20 06:08:09 UTC
(In reply to Petr Hracek from comment #10)
> See upstream comments and feel free to comment it.
> https://github.com/rear/rear/pull/1022

Thanks.

Comment 13 Jakub Mazanek 2017-02-23 14:55:21 UTC
rebase to rear-2.00 will fix this issue

Comment 19 errata-xmlrpc 2017-08-01 22:19:55 UTC
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


Note You need to log in before you can comment on or make changes to this bug.