The fix-permissions and update-package-permissions scripts check whether the $RUNAS user is opennms. If it is not, they print a message stating that $RUNAS has been changed from the default 'opennms' user. Assuming you know what you're doing and not changing ownership of any files. , then exit with status 0.

This leaves the installation in an inconsistent state, with some files owned by the $RUNAS user and some owned by the opennms user, which requires additional steps by the sys admin.

The parts of the scripts that perform the file ownership change still use the value of the $RUNAS variable, and are not hardcoded to use the opennms user.

These scripts should update file ownership to match the $RUNAS user instead of bailing.