Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Invalid
-
None
-
None
-
None
-
None
Description
When I query for process status through something like this:
falcon instance -type process -name XYZ -start 2014-08-31T12:00Z -end 2014-09-02T00:00Z -status
and if the process was updated on certain date in middle of the start and end range, the request returns an error like:
Error: Start date 2014-08-31T12:00Z is before PROCESS's start 2014-09-01T12:00Z for cluster ABC
Ideally, the expected behavior should be for the request to be handled in such a way, that the status is returned correctly for all the instances despite multiple process updates.