a state where a package has the status: install ok not-installed should never have the field "Auto-Installed: yes". The result is that the package in that state will prevent any operation from succeeding, as the solver will fail (libsolv backend). It's not completely clear how to get the system into this state. This is happening intermittently on hardware running as part of an automated test suite. Live changes are being pushed to the feeds the targets are referencing. This includes renaming some packages. It seems that devices with a package installed under the old name would update to the latest version of the feed, see that packages now depended on the new package name, and try to fix it, resulting in a package in the state described above.
Issue only happens on libsolv backend
fixed on c23fab68e57d3dc6632c1699d662c23a83ce7214