-
Notifications
You must be signed in to change notification settings - Fork 396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module schemas are not installed when enabling a module via config when running blt deploy #718
Comments
I ran into the same issue, but with the flag module. I haven't debugged to the point where I overrode the setup:update target and ran config import manually, but can try that out tonight. |
I'm pretty sure this is an upstream bug with how Drush handles the My understanding was that it was fixed in newer versions of Drush though. |
Hmm. That issue in the drush queue certainly describes what I'm seeing, but I'm running drush 9.0.0-alpha1 and the issue was supposedly fixed in 8.1.0 drush-ops/drush#2069 (comment) edit but 9.0.0-alpha1 is older than 8.1.0. Sigh. Ok, I'm closing this issue since it seems the fault is not with BLT. |
Thanks for digging into the version issue. I was pretty confused as well, but that would explain it. @grasmash this has probably been rehashed endlessly, but do you think BLT should ship Drush 8 instead of Drush 9? Or maybe we should pester the Drush maintainers to roll 9.0.0-alpha2. |
It looks like Lightning requires Drush 9. I don't see that BLT defines a specific version dependency. I've pinged the Lightning maintainers to see if it's viable for them to use drush 8 instead: https://github.com/acquia/lightning/issues/233 |
We do declare drush as a dependency. Projects are welcome to change that individually, although I think we have to stay in step with Lightning. |
Actually it looks like Lightning just downgraded, so maybe we should too. I'll reopen this issue so it stays on the radar. @grasmash seems like we should downgrade Drush to 8.x |
I would like to downgrade to Drush 8. I believe I ran into Drupal Console related issues when doing so. |
I can also confirm I'm seeing this issue while deploying to Acquia remote environments. Although I'm seeing it manifest when simply updating configuration values. I get the following output on the Workflow console: [16:41:37] [16:41:37] Started
[16:41:51] [2016-12-02 16:41:46] Starting hook: post-code-update
[2016-12-02 16:41:46] Executing: /mnt/users/[removed]/dev.shell /var/www/html/[removed].dev/hooks/common/post-code-update/post-code-update.sh [removed] dev master master [removed].git git < /dev/null (as [removed])
Running updates for environment: dev
Buildfile: /var/www/html/[removed]/vendor/acquia/blt/phing/build.xml
blt > deploy:update:
blt > setup:update:
blt > setup:toggle-modules:
acquia_connector is already enabled. [ok]
shield is already enabled. [ok]
There were no extensions that could be enabled. [ok]
Extension devel was not found and will not be uninstalled. [warning]
field_ui is already uninstalled. [ok]
views_ui is already uninstalled. [ok]
There were no extensions that could be uninstalled. [ok]
Collection Config Operation
shield.settings update
Import the listed configuration changes? (y/n):
y
Argument 1 passed to _drush_config_import_partial() must be an [error]
instance of Drupal\Core\Config\FileStorage, instance of
Drush\Config\StorageWrapper given, called in
/mnt/www/html/[removed]/vendor/drush/drush/includes/drush.inc
on line 725 and defined config.drush.inc:687
E_RECOVERABLE_ERROR encountered; aborting. To ignore recoverable [error]
errors, run again with --no-halt-on-error
Drush command terminated abnormally due to an unrecoverable error. [error]
[phingcall] /var/www/html/octagon.dev/vendor/acquia/blt/phing/tasks/setup.xml:244:32: Drush exited with code 255
BUILD FAILED
/var/www/html/[removed].dev/vendor/acquia/blt/phing/tasks/deploy.xml:161:22: Execution of the target buildfile failed. Aborting.
Total time: 4.0136 seconds
Update errored.
Finished updates for environment: dev
[2016-12-02 16:41:51] Finished hook: post-code-update |
BLT has been downgraded to Drush 8 by default. This should resolve this issue. |
Problem summary
I installed and configured the Redirect module on my local environment, exported config and ran
blt deploy
to push the code up. The deploy command completed successfully, but the environment throws errors because the table which the module defines is not present in the database.The config for the module was imported though, and core.extension shows the module as enabled.
Drush pmi
shows the module as not installed though. Attempting rundrush en
says the module is enabled. Runningdrush pm-uninstall
says it is not enabled.In testing, when I overrode the setup:update target to not run the config-imports and instead ran config-import manually when the deploy was complete, the table was installed and the module worked as expected.
My system information:
Output of
blt doctor
:The text was updated successfully, but these errors were encountered: