SQL Error After 1.8 to 1.8.1 Upgrade

Using Docker and docker-compose.

I got these errors after the upgrade from 1.8 to 1.8.1

Unable to rollback. E = SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'objectId' cannot be null

And

	#0 /var/www/cms/lib/Entity/Upgrade.php(79): PDO->exec('UPDATE `permiss...') #1 /var/www/cms/lib/Controller/Upgrade.php(128): Xibo\Entity\Upgrade->doStep() #2 [internal function]: Xibo\Controller\Upgrade->doStep('2') #3 /var/www/cms/vendor/akrabat/rka-slim-controller/RKA/Slim.php(79): call_user_func_array(Array, Array) #4 [internal function]: RKA\Slim->RKA\{closure}('2') #5 /var/www/cms/vendor/slim/slim/Slim/Route.php(468): call_user_func_array(Object(Closure), Array) #6 /var/www/cms/vendor/slim/slim/Slim/Slim.php(1357): Slim\Route->dispatch() #7 /var/www/cms/vendor/slim/slim/Slim/Middleware/Flash.php(85): Slim\Slim->call() #8 /var/www/cms/vendor/slim/slim/Slim/Middleware/MethodOverride.php(92): Slim\Middleware\Flash->call() #9 /var/www/cms/lib/Middleware/Actions.php(141): Slim\Middleware\MethodOverride->call() #10 /var/www/cms/lib/Middleware/Theme.php(35): Xibo\Middleware\Actions->call() #11 /var/www/cms/lib/Middleware/WebAuthentication.php(132): Xibo\Middleware\Theme->call() #12 /var/www/cms/lib/Middleware/CsrfGuard.php(62): Xibo\Middleware\WebAuthentication->call() #13 /var/www/cms/lib/Middleware/State.php(109): Xibo\Middleware\CsrfGuard->call() #14 /var/www/cms/lib/Middleware/Storage.php(47): Xibo\Middleware\State->call() #15 /var/www/cms/lib/Middleware/Xmr.php(36): Xibo\Middleware\Storage->call() #16 /var/www/cms/vendor/slim/slim/Slim/Slim.php(1302): Xibo\Middleware\Xmr->call() #17 /var/www/cms/web/index.php(124): Slim\Slim->run() #18 {main}

I skipped the step and tested. All seems fine. I still have a backup, so I will test the CMS a bit before I commit. Just an FYI. If it is something I need to address now please let me know.

Thanks

I think this has already been resolved and an updated container was published.

It’s possible you got in there before the fix was published.

Assuming you have no custom display permissions then I don’t think skipping the step should have caused any issues. If you do, you’ll want to check and re-apply those as applicable, or roll back, and upgrade again after running

docker-compose pull

Thanks for the report though.