Description of problem: In the Data Center main tab you can sort DCs by all the fields except the compatibility version. Version-Release number of selected component (if applicable): [ovirt@localhost ~]$ rpm -qa | grep ovirt-engine ovirt-engine-lib-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-setup-plugin-ovirt-engine-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-setup-plugin-websocket-proxy-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-jboss-as-7.1.1-1.el6.x86_64 ovirt-engine-tools-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-websocket-proxy-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-extensions-api-impl-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-restapi-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-backend-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-setup-base-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-userportal-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-setup-plugin-ovirt-engine-common-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-cli-3.5.0.2-1.el6.noarch ovirt-engine-webadmin-portal-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-sdk-python-3.5.0.3-1.el6.noarch ovirt-engine-dbscripts-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch ovirt-engine-setup-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch How reproducible: 100% Steps to Reproduce: 1. Open the Data Centers main tab 2. Click on the "Compatibility Version" header Actual results: Nothing happens Expected results: Column should sort in ascending order Additional info: IIUC, the root cause of this issue is bug 1124375. I'm currently opening both issues and marking this one as blocked by 1124375 so they can both be verified. If you think this is redundant, feel free to close this one as a duplicate.
Removed BZ dependency since bugs are not related
verified ovirt-engine-3.5.0-0.0.master.20140804172041.git23b558e.el6.noarch
oVirt 3.5 has been released and should include the fix for this issue.