Hello,
I have recently started using Ægir with some D8 sites, today I installed a site and replaced the database with a local one, containing all my content and configuration for it, so far so good, nothing different from the usual.
However now I can't verify the site from aegir anymore because drush fails the task.

The reported error is:

Undefined property: stdClass::$version packages_8.inc:52	
-
Creating default object from empty value packages_8.inc:80	
-
Drush command terminated abnormally due to an unrecoverable error. Error: Cannot use object of type stdClass as array in /var/aegir/.drush/provision/platform/drupal/packages_8.inc, line 89	
-
The external command could not be executed due to an application error.	
-

The only different thing from the usual is that the site is built using the minimal install profile and I normally used the standard, could this be related?
I'm mentioning because I noticed that for some reason Ægir does not allow the creation of sites in D8 with the minimal install profile.

I will try to reproduce to understand if this is the source of the issue, in the meanwhile any hint is appreciated.

CommentFileSizeAuthor
#2 d8-verify-error-2661124-2.patch739 byteskristofferwiklund
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

esolitos created an issue. See original summary.

kristofferwiklund’s picture

Status: Active » Needs review
FileSize
739 bytes

I had the same problem when doing a Remote import of a D8 site from an other server.

But the attach patch fixes it.

kristofferwiklund’s picture

Fix needed in Provision instead #2665596: D8 site verify problem.

kristofferwiklund’s picture

gboudrias’s picture

Project: Hosting » Provision

gboudrias’s picture

Status: Needs review » Fixed

I pushed kristofferwiklund's patch after testing site creation and verification on both D7 and D8.

This was pretty clearly a typo in the provision code. Thanks for the patch, esolitos please reopen if the problem persists after applying it.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.