Red Hat Bugzilla – Bug 1287827
[RFE] replicators: when no events exists for the replicators the timeline button becomes greyed out
Last modified: 2017-08-28 11:10:17 EDT
Created attachment 1101594 [details]
logs and screenshot
Description of problem:
This only happens to replicators and not to pods/containers.
However, I think it's wrong behaviour and that the button should always be available and if no events exists simply say that in the query.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a replicator and delete the event from db or... add an existing openshift provider with a very old replicator running which no longer has any events on it
2. navigate to containers -> replicator
3. select the relicator -> monitoring -> timeline
timeline is greyed out
timeline should not be greyed out but we should be able to select it and get a message that no events exists for the replicator
Additional info: screen shot and logs attached
That is the correct behavior across UI to disable/grey out Timelines button when there are no events available for an object.
I think this is not an issue, so the BZ should be closed.
honestly I think that current behaviour looks like a bug which is why I opened it :) I think it's much better to allow selection and report that no events exist for the object.
I understand that this is the current agreed behaviour but speaking from a user prospective I think it should be changed and do not think this bug should be closed.
Having said that, I have no objections to change this to an RFE so it could be discussed in future.
I think this should be changed to RFE, since that's the existing behavior for all Timelines buttons across the UI.
(In reply to Harpreet Kataria from comment #3)
> I think this should be changed to RFE, since that's the existing behavior
> for all Timelines buttons across the UI.
We do not have an RFE component so I am not sure how to do that.
According to comment 1 this is not related to containers.
This bug has been open for more than a year and is assigned to an older release of CloudForms.
If you would like to keep this Bugzilla open and if the issue is still present in the latest version of the product, please file a new Bugzilla which will be added and assigned to the latest release of CloudForms.