Description of problem: I think there should be information about last synchronization with all Ceph clusters. This synchronization is done every 24 hours but admin should know when it was done last time. I expect that this info is now in logs but logs can rotate and it is not easy to find it in logs. Version-Release number of selected component (if applicable): ceph-ansible-1.0.5-15.el7scon.noarch ceph-installer-1.0.11-1.el7scon.noarch rhscon-ceph-0.0.19-1.el7scon.x86_64 rhscon-core-0.0.20-1.el7scon.x86_64 rhscon-ui-0.0.34-1.el7scon.noarch Expected results: There will be info about last synchronization for all Ceph clusters.
I agree that showing that showing the last refreshed/updated would be useful. It may make more sense to show this on a per cluster basis. We could potentially show this in object details, tooltip on status details, or some other places that make sense. We'll look into this and see where best to show it. Suggest this to be low to medium priority.
Created attachment 1166413 [details] Tooltip showing last synced time I've attached a quick wireframe to show how this tooltip should appear. Please reflect the current status and date/time of last sync.
Sounds like something that will need some bit of communication with backend engineering to get this to work. Better be done by Karnan, as he'll be more focused towards api/backend related bugs (as I'm traveling & working more on non-API/UX bugs).
setting up the bug priority as per PM priority.
There is tooltip with last date of synchronization and it is correct. Status is missing -> Assigned Tested with ceph-ansible-1.0.5-25.el7scon.noarch ceph-installer-1.0.12-4.el7scon.noarch rhscon-ceph-0.0.32-1.el7scon.x86_64 rhscon-core-0.0.33-1.el7scon.x86_64 rhscon-core-selinux-0.0.33-1.el7scon.noarch rhscon-ui-0.0.47-1.el7scon.noarch
Tested with ceph-ansible-1.0.5-31.el7scon.noarch ceph-installer-1.0.14-1.el7scon.noarch rhscon-ceph-0.0.36-1.el7scon.x86_64 rhscon-core-0.0.36-1.el7scon.x86_64 rhscon-core-selinux-0.0.36-1.el7scon.noarch rhscon-ui-0.0.50-1.el7scon.noarch and it works.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2016:1754