Description of problem: "docker events --until" reports the events created even after the specified timestamp Version-Release number of selected component (if applicable): docker-io-1.2.0-2.fc20.x86_64 How reproducible: Steps to Reproduce: 1. Listen for events till 2014-11-03T20:26:59+05:30 # Shell 1: docker events --until='2014-11-03T20:26:59+05:30' # Shell 2: docker start f394b1d ; docker stop f394b1d 2014-11-03T20:24:59+05:30 f394b1d: (from akalliya/wild-fly:latest) start 2014-11-03T20:25:05+05:30 f394b1d: (from akalliya/wild-fly:latest) die 2. Wait for the mentioned time to get over. Then open a terminal and start/stop the container. Actual results: docker events commands running on Shell1 still reports the events created after the specified time (2014-11-03T20:26:59+05:30) . 2014-11-03T20:27:12+05:30 f394b1d: (from akalliya/wild-fly:latest) start 2014-11-03T20:28:15+05:30 f394b1d: (from akalliya/wild-fly:latest) die Is this a bug ? Expected results: docker events --until " " should not log any events created after the specificed time. Additional info:
Andreas are you working on this one?
Lokesh can you verify this one with docker-1.3.1
amrithakalliyat are you still seeing this with docker-1.5?
shishir can you check if this one is fixed?
This one is fixed in upstream. After the `--until` timestamp, `docker events` command will die. Changing it to modified. Shishir
Fixed in docker-1.6?
Issue exists on fedora 21 docker. Docker version: Client version: 1.5.0 Client API version: 1.17 but it's fixed in upstream 1.6.0 which will be released this Friday. Shishir
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days