Hi,

If one invokes provision-save (CLI) for a site without a '--profile' parameter .. the drush alias generated sets the sites profile to 'default' ..

With the site's profile set to 'default', a later invocation of provision-install (CLI) for that site will fail .. even if provision-install was invoked with an argument --profile='standard' ..

The failure is in creating a database .. although the drush tasks invoked by provision-install prints out an OK to the task of 'Created database ' .. the database does not actually get created and a login to the DB will confirm that.

Without a database, the provision-install eventually fails with the standard PDOException (about table or view not found) and goes even further to delete the site context from drush aliases ..

Possible fix(es):
-- use a default --profile of 'standard' for provision-save
-- don't ignore --profile for 'provision-install' ..

Versions in use:
Aegir3 Beta 1
Modules: hosting 7.x-3.0-beta1+9-dev

Comments

chuxau’s picture

I see now this stems from the renaming of the default install profile from 'default' to 'standard' .. A simple patching of the following files would fix this ..

platform/import.provision.inc (line 24)
Context/site.php (lines 19,42 .. 19 is just for documentation generation)

Hopefully be able to contribute small patches like this soon

ergonlogic’s picture

We've already switched the default profile to 'standard' in the front-end, iirc. So, it'd make sense to do that here too.

Ignoring --profile in provision-install should be investigated. Is it just ignored, or is it throwing a warning/error. If the latter, perhaps try with --strict=0.

chuxau’s picture

Thanks for the quick response, ergonlogic ..

It seems to be just ignoring it, no errors are displayed

  • helmo committed e17314e on 7.x-3.x
    Issue #2468203: provision-save: default profile from 'default' to '...

  • helmo committed e17314e on 7.x-4.x
    Issue #2468203: provision-save: default profile from 'default' to '...
helmo’s picture

Status: Active » Fixed

The commit above should resolve this... please re-open if the problem remains.

Status: Fixed » Closed (fixed)

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