With an software as old as opsi it is sometimes inevitable to stumble over something and then be left scratching your head.
One of this cases I recently discovered in
Whenever an package is installed it is made in a way that ignores the lock of the product on the depot.
The lock is in place to avoid problems where multiple tools would (un)install the same product. This could result in problems which leave the system in an undefined state regarding the product installation - something that should be avoided!
With opsi-utils 220.127.116.11 we do not ignore the lock anymore. If a locked product is detected no installation will be made but we will abort with an error instead. This may lead to problems coming to the surface which may have been hidden before, especially when having a heavily automated setup, but we think not knowing about the problem is far worse. The problems probably have been there before but were usually not in sight.
If you run into such an problem now you should take a look at the logs and find out what is causing your problem.
Once you figured this out and resolved it you can use
opsi-package-manager --install --force /var/lib/opsi/repository/<packagefile>.opsi to make install the package in way that ignores the locked state of the product.
If everything works you can run
opsi-package-updater again to finish what was started.