Moran, can you please review this bug?
Should not be that complicated and can save time to many people by having that info available together with the rest of the packages we show today.

We probably should reduce the number of packages we display. It's endless (then they'll ask for multipath, LVM, ...).

The solution is an Ansible playbook that can provide this via facts or so. Should be fairly easy, I assume.

(In reply to Marina from comment #1)
> Moran, can you please review this bug?
> Should not be that complicated and can save time to many people by having
> that info available together with the rest of the packages we show today.

I tend agree with Yaniv here, and actually was on my list to discuss with you.
let's understand what problem displaying this information solve. my claim is it would sit 99% useless (similar to other packages versions) and only in the case of problem (migration of hosted engine) it would come to play for debugging purposes. and an Ansible playbook that would collect all the packages data from the hosts in the system and possibly do quick parsing of misaligned versions would serve this purpose much better.

I would like to close this one, please let me know if you have any additional thoughts/comments on this approach.

BZ<2>Jira Resync