[Bugs] [Bug 1362151] [libgfchangelog]: If changelogs are not available for the requested time range, no proper error message

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1362151



--- Comment #2 from Kotresh HR <khiremat at redhat.com> ---
NOTE: The steps to reproduce mentioned in #Description is incorrect hence
restating the problem description and steps to reproduce.

Description of problem:

 If changelogs are not available for the requested time range, no proper error
message is displayed. It just fails. If start time is less than min changelog
available time, then history changelog fails with -1 as any failure and no
error message is printed. Distinguishing this error will be helpful for 
the consumers to act upon it.

For example, geo-replication upon receiving this error would fallback to
xsync. 

Version-Release number of selected component (if applicable):
mainline

How reproducible:
Always

Steps to Reproduce: (For simplicity consider plain distribute setup)
This is not simple to reproduce. It might hit during replace brick scencarios.
1. Setup geo-rep between master and slave
2. Before geo-rep syncs all data from master to slave, replace the brick from
   master and write new data on master.
3. Now the replaced brick's min changelog available is much later than the
   stime (sync time) corresponding to this brick.
4. When geo-rep is started after replace brick, it would hit above case.


Actual results:
When start time is less than min available changelog, histor fails with -1 and
error is not logged.

Expected results:
It should distinguish the above error, log it and fail.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=S9rLuLX6yu&a=cc_unsubscribe