Error: Class 'EntityInlineEntityFormController' not found on command updb

That should just be a warning and not a fatal error. Can you keep running the update script until the error goes away?

What previous version were you upgrading from?

Might also check to see if the inline_entity_form module is enabled or not.

OK, that's a new dependency of bootstrap_tour and it looks like it's not getting enabled in any update hook.

Enable the inline_entity_form module first and then run the update.php (drush updb)

Note: If you are not able to use drush commands, you can temporarily move the bootstrap_tour module from /profiles/openatrium/modules/contrib/bootstrap_tour to your /tmp directory, then enable inline_entity_form via drush, and then move the bootstrap_tour module back into its original location.

Did you revert your Features after running updates?

Also, looks like you don't have the oa_related module enabled. Although that module *is* enabled normally via an update hook, so not sure why that's not enabled on your site.

(oa_related was part of 2.33 so maybe you disabled it on purpose?)

Also, if you get any error during update script, be sure to run it again in case it didn't finish.

Cool, thanks for the heads up on this. I added a note to the Release Notes pointing people to this issue if they have the same trouble.

Also, related to comment #7, I committed a fix to oa_comment -dev version to fix the error generated when oa_related is disabled.

This happens on every installation that tries to update to 2.40, so changing to major.

If I try to enable the inline_entity_form module BEFORE running update.php, I get the following errors (on Pantheon):

class_implements(): Class BootstrapTourEntityController does not       [warning]
exist and could not be loaded entity.module:1474
in_array() expects parameter 2 to be array, boolean given              [warning]
entity.module:1474
class_implements(): Class BootstrapTourEntityController does not       [warning]
exist and could not be loaded entity.module:84
in_array() expects parameter 2 to be array, boolean given              [warning]
entity.module:84
WD bootstrap_tour_step: PDOException: SQLSTATE[42S02]: Base table or     [error]
view not found: 1146 Table 'pantheon.bootstrap_tour_step' doesn't
exist: INSERT INTO {bootstrap_tour_step} (path, selector, placement,
title, content, content_text_format) VALUES
(:db_insert_placeholder_0, :db_insert_placeholder_1,
:db_insert_placeholder_2, :db_insert_placeholder_3,
:db_insert_placeholder_4, :db_insert_placeholder_5); Array
(
    [:db_insert_placeholder_0] => node/add/oa-space
    [:db_insert_placeholder_1] => #edit-field-oa-banner-position-und
    [:db_insert_placeholder_2] => right
    [:db_insert_placeholder_3] => Space Banner
    [:db_insert_placeholder_4] => Select a banner image to be
uploaded.  Banner images should have an aspect ratio appropriate
for streching across the full width of the site.
    [:db_insert_placeholder_5] => panopoly_wysiwyg_text
)
 in drupal_write_record() (line 7337 of
/srv/bindings/c788c1c8b44f48dab9398da6831a06af/code/includes/common.inc).
WD php: PDOException: SQLSTATE[42S02]: Base table or view not found:     [error]
1146 Table 'pantheon.bootstrap_tour_step' doesn't exist: INSERT INTO
{bootstrap_tour_step} (path, selector, placement, title, content,
content_text_format) VALUES (:db_insert_placeholder_0,
:db_insert_placeholder_1, :db_insert_placeholder_2,
:db_insert_placeholder_3, :db_insert_placeholder_4,
:db_insert_placeholder_5); Array
(
    [:db_insert_placeholder_0] => node/add/oa-space
    [:db_insert_placeholder_1] => #edit-field-oa-banner-position-und
    [:db_insert_placeholder_2] => right
    [:db_insert_placeholder_3] => Space Banner
    [:db_insert_placeholder_4] => Select a banner image to be
uploaded.  Banner images should have an aspect ratio appropriate
for streching across the full width of the site.
    [:db_insert_placeholder_5] => panopoly_wysiwyg_text
)
 in drupal_write_record() (line 7337 of
/srv/bindings/c788c1c8b44f48dab9398da6831a06af/code/includes/common.inc).
Cannot modify header information - headers already sent by (output     [warning]
started at /opt/drush5/includes/output.inc:37) bootstrap.inc:1257
PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'pantheon.bootstrap_tour_step' doesn't exist: INSERT INTO {bootstrap_tour_step} (path, selector, placement, title, content, content_text_format) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5); Array
(
    [:db_insert_placeholder_0] => node/add/oa-space
    [:db_insert_placeholder_1] => #edit-field-oa-banner-position-und
    [:db_insert_placeholder_2] => right
    [:db_insert_placeholder_3] => Space Banner
    [:db_insert_placeholder_4] => <p><span>Select a banner image to be uploaded. &nbsp;</span></p><p><span>Banner images should have an aspect ratio appropriate for streching across the full width of the site.</span></p>
    [:db_insert_placeholder_5] => panopoly_wysiwyg_text
)
 in drupal_write_record() (regel 7337 van /srv/bindings/c788c1c8b44f48dab9398da6831a06af/code/includes/common.inc).
Drush command terminated abnormally due to an unrecoverable error.       [error]

But the inline_entity_form module DOES get enabled, and the update runs fine. Even for an update that includes both 2.30 and 2.40.

For the release notes;

IF UPDATING from a previous version of Open Atrium, you might need to enable the inline_entity_form module BEFORE you run the Update.php (drush updb) script.

EVERYONE is updating from a previous version of Open Atrium, so this should be changed into:

You need to manually enable the inline_entity_form module BEFORE you run the Update.php (drush updb) script.

This was marked as fixed because the procedure given in #6 fixes it for people who cannot enable the inline_entity_form.

Working on a 2.41 release to handle this better also.

The wording in the release notes is correct because not everybody is upgrading, some are installing fresh. And it doesn't happen on every site we have upgraded (which is why this wasn't caught before release).

Cheers for releasing a fixed version so quick!