I've added COD version 7.x-1alpha3 to BOA and it verified platform successfully.

However, when I tried to create a site from it, it failed in:

Running: /data/disk/o1/tools/drush/drush.php --client_email='o1_do@bluefish.rs' @c2.kovac.biz provision-install-backend --backend 2>&1
Undefined offset: 1 backend.inc:163
Undefined variable: output backend.inc:170
The command could not be executed successfully (returned: Segmentation fault , code: 139)

Afterwards, I exchanged code in same place/name for Omega8 Drupal 7.23.3 and it verified and produced a site.

The platform verified both with standard COD-7.x-1alpha3 code and with COD-7.x code with added Omega Drupal 7.23.3 code, but failed to produce the site with same error.

Any idea? (beside: do not use distributions that are not included ;)

Comments

omega8cc’s picture

omega8cc CreditAttribution: omega8cc commented
Category: Bug report » Support request
Status: Active » Closed (won't fix)

Do not expect it to work, yet. Plus any such issues should be reported in the COD queue, not in the Octopus queue. We have COD 7.x added as unsupported (so for testing only) in the current BOA release.

MacMladen’s picture

MacMladen CreditAttribution: MacMladen commented

The real question was Why it passes verify and then fail on install?

Not that I actually need COD but was wondering about flaw in process (verify: OK, install: FAIL), is there something that can be done to avoid successful verification on something that later fails?

Or should failed installation also render platform not verified to prevent confusion and further install fails?

Also, because it fails to finish, it is impossible to delete it, so it have to be removed manually (.../node/12345/delete hack)

omega8cc’s picture

omega8cc CreditAttribution: omega8cc commented

This is normal. Platform verify task doesn't run the installation (profile) procedure, it only prepares the platform for that procedure. You should submit any such bugs in the correct (COD) queue.