[Bugs] [Bug 1207028] New: [Backup]: User must be warned while running the 'glusterfind pre' command twice without running the post command

[bugzilla at redhat.com]

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

            Bug ID: 1207028
           Summary: [Backup]: User must be warned while running the
                    'glusterfind pre' command twice without running the
                    post command
           Product: GlusterFS
           Version: mainline
         Component: unclassified
          Assignee: bugs at gluster.org
          Reporter: sanandpa at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:

As per the sequence of steps to be followed, 'glusterfind create' is to be
followed with a 'pre' and a 'post' to generate the list of changed files, and
to update the timestamp to the latest one, respectively. There would be times
when the admin might forget to run the 'post' step, thereby forgetting to
update the timestamp, resulting in an incorrect list of changed files.

When any 'glusterfind pre' command is given, we could have a check if the
'glusterfind post' command has been executed or not.. by simply checking the
existence of 'status.pre' file in the $SESSION_DIR location, or by any other
means. A confirmation message to the user letting him know that the
'glusterfind post' command is not run, and would he still like to continue,
would help.

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

Glusterfs upstream nightly glusterfs-3.7dev-0.777.git2308c07.el6.x86_64

How reproducible: 

Easily.
This would particularly happen if the user chooses to NOT use the wrapper
script that we are going to provide, and goes ahead with the CLI commands


Steps to Reproduce:
1. Have a glusterfs volume, create a session using 'glusterfind create'
2. Create new files in the volume
3. Run 'glusterfind pre' command
4. Check the output file if it has a mention of files created in step2
5. Create more new files in the volume
6. Again run 'glusterfind pre' command
5. Check the output file if it has a mention of files created in step2 as well
as step5


Actual results:

Step6 should ask the user for a confirmation stating something like this:

"Glusterfind post command has not been run after running the pre command last
time. This would result in an aggregated list of changed files. Would you still
like to continue? Y/N "

Expected results:

No warning is given

Additional info:

[root at dhcp43-140 ~]# rpm -qa | grep glusterfs
glusterfs-regression-tests-3.7dev-0.777.git2308c07.el6.x86_64
glusterfs-3.7dev-0.777.git2308c07.el6.x86_64
glusterfs-extra-xlators-3.7dev-0.777.git2308c07.el6.x86_64
glusterfs-resource-agents-3.7dev-0.777.git2308c07.el6.noarch
glusterfs-debuginfo-3.7dev-0.777.git2308c07.el6.x86_64
glusterfs-libs-3.7dev-0.777.git2308c07.el6.x86_64
glusterfs-api-3.7dev-0.777.git2308c07.el6.x86_64
glusterfs-devel-3.7dev-0.777.git2308c07.el6.x86_64
glusterfs-cli-3.7dev-0.777.git2308c07.el6.x86_64
glusterfs-server-3.7dev-0.777.git2308c07.el6.x86_64
glusterfs-geo-replication-3.7dev-0.777.git2308c07.el6.x86_64
glusterfs-rdma-3.7dev-0.777.git2308c07.el6.x86_64
glusterfs-ganesha-3.7dev-0.777.git2308c07.el6.x86_64
glusterfs-fuse-3.7dev-0.777.git2308c07.el6.x86_64
glusterfs-api-devel-3.7dev-0.777.git2308c07.el6.x86_64
[root at dhcp43-140 ~]#

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.