WD cron: EntityFieldQueryException: Unknown field: field_oa_date in EntityFieldQuery->addFieldCondition

Do you have any Event Import feeds? (using oa_events_import) Make sure you have the oa_events module enabled as that defines the field_oa_date field.

I just tried the same thing.

drush dl openatrium
It got me a tree with openatrium-7.x-2.0-beta4, and let Aegir install a site using the Openatrium install profile.

I doubt @SocialNicheGuru ahs any Event Import feeds as it is failing during site installation.
I can confirm that the oa_events module is enabled at the point of this error. See the attached file for a full log.

Sounds like a caching issue with Aegir and Features that is not creating the field_oa_date at the correct time. I don't see this in either "drush site-install" or in the interactive install.php which is all I can really test/support.

Can somebody try either #1597186: Do not cache included components in features_include_defaults() and/or #1572578: Rethink the way features are enabled / disabled to see if those patches to Features help with this issue at all?

In #2063589: Allow site install errors to be ignored we discovered that running an 'Enable' task on the site makes it 'functional'.

The patch from https://drupal.org/node/1597186#comment-7842229 fixes the "WD cron: EntityFieldQueryException: Unknown field: field_oa_date" error.
The Aegir install task is still marked as having an error, but did not 'fail' to enable the site.

The remaining error is:
WD search_api_solr: SearchApiException while deleting an index's data: "0" Status: Request failed: Connection refused in SearchApiSolrConnection->checkResponse() (line 548 of /var/aegir/platforms/openatrium-7.x-2.0-beta4/profiles/openatrium/modules/contrib/search_api_solr/includes/solr_connection.inc).

And two remaining warnings:

The following views were using the index Database Node Index: panopoly_database_search. You should disable or delete them.
The following views were using the index Solr Node Index: panopoly_search. You should disable or delete them.

The patch from https://drupal.org/node/1572578#comment-7839439 fixes this even better! now the SearchApiException and two warnings from above are also gone.

Excellent, thanks for testing that and posting. Those 2 patches have been on my radar but I just haven't had time to play with them in Open Atrium yet. All I need to do is a quick performance test to make sure they don't do anything bad to the normal drupal install.php process and then I can get them committed to Features and then to OA2.

These patches were committed to Features and oa_core.make has been updated to use the latest 2.0-rc5 Features.