Comment 8 for bug 1689608

Kathy,

When you say you loaded it onto a master system, do you mean you used the upgrade script against an existing database, or that you cherry-picked the commit onto a new master branch? If the latter, the current branch is rebased to very recent master, so that shouldn't be necessary...

Can you capture the error that starts the failure? It looks like there is a problem with the container or action schema files, but I'm not seeing anything strange looking at the code.

Also, I've force-pushed an update as the upgrade script needed to be adjusted WRT the permission id -- that was one of the baseline schema conflicts, and I hadn't touched the upgrade.

Thanks!