Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Events are not properly ordered #1846

Closed
jorgemoralespou opened this issue Jul 14, 2017 · 5 comments
Closed

Events are not properly ordered #1846

jorgemoralespou opened this issue Jul 14, 2017 · 5 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/P2
Milestone

Comments

@jorgemoralespou
Copy link

jorgemoralespou commented Jul 14, 2017

Doing a build, I go to the events and see:

image

NOTE: Events are sorted by time in the UI.

Which don't make much sense in that order.
I verify that command line the events are ordered.

LASTSEEN   FIRSTSEEN   COUNT     NAME           KIND          SUBOBJECT                    TYPE      REASON                         SOURCE                   MESSAGE
4m         4m          1         test-1-build   Pod                                        Normal    Scheduled                      default-scheduler        Successfully assigned test-1-build to localhost
4m         4m          1         test-1-build   Pod           spec.containers{sti-build}   Normal    Pulling                        kubelet, localhost       pulling image "openshift/origin-sti-builder:v3.6.0-rc.0"
4m         4m          1         test-1-build   Pod           spec.containers{sti-build}   Normal    Pulled                         kubelet, localhost       Successfully pulled image "openshift/origin-sti-builder:v3.6.0-rc.0"
4m         4m          1         test-1-build   Pod           spec.containers{sti-build}   Normal    Created                        kubelet, localhost       Created container
4m         4m          1         test-1-build   Pod           spec.containers{sti-build}   Normal    Started                        kubelet, localhost       Started container

Version v3.6.0-rc0

@spadgett spadgett added the kind/bug Categorizes issue or PR as related to a bug. label Jul 14, 2017
@spadgett spadgett self-assigned this Jul 14, 2017
@spadgett
Copy link
Member

We sort by newest first in the UI, but it looks like the events might have the same timestamp.

@jorgemoralespou
Copy link
Author

@spadgett depends on the time granularity. As you can see in the command line output, they are properly ordered, that means that either they come in order from the API query, or that they have miliseconds granularity. In the web ui, there is no miniseconds granularity, so I guess that ordering of things that happens in the same second can be not in the real order they happened.

@spadgett
Copy link
Member

As far as I can tell, the API response is coming back with only second granularity and the events are not returned in order.

@fabianofranz How is the CLI sorting events?

@fabianofranz
Copy link
Member

In oc get we don't sort by default, just display them in the order it comes from the API.

@jorgemoralespou
Copy link
Author

I hope the API does return them sorted as otherwise would be awkward to look at a big list of events.

@spadgett spadgett modified the milestones: 1.4.0, 3.7.0 Sep 13, 2017
openshift-merge-robot added a commit that referenced this issue Oct 30, 2017
Automatic merge from submit-queue.

Add resourceVersion as a secondary sort for events

Fixes #1846

/assign @jwforres
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/P2
Projects
None yet
Development

No branches or pull requests

3 participants