Comment 4 for bug 1796932

Latest git of virt-manager builds fine.
But that is due to [1] which is a nice development, but not ok as a "bugfix" for the current issue.

Furthermore there is no released version of virt-manager with that code yet, so it might be unverified and has some rough edges.
It is unlikely that we can jump onto this new "wagon" right now, more likely to happen with a release of virt-manager 1.6

The above explains why upstream virt-manager might not have seen it yet, but we need a fix for the sorting of silverblue28 breaking the test.
But the test might show a real issues and real functionality might be broken - therefore I'd not just want to disable the test either.

So we need a fix that fixed virt-manager 1.5.x stream and/or for now remove the bad osdb entry that exposes the issue.

[1]: https://github.com/virt-manager/virt-manager/commit/d52d9885c85623b8d924dbf0aceecb08b33e9122