Skip to content
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

updatedb fails to run updates when status checks fail #3316

Closed
rbayliss opened this issue Jan 18, 2018 · 3 comments
Closed

updatedb fails to run updates when status checks fail #3316

rbayliss opened this issue Jan 18, 2018 · 3 comments
Assignees

Comments

@rbayliss
Copy link
Contributor

rbayliss commented Jan 18, 2018

Running drush updatedb -y on Drush 9.x-dev fails to run update hooks when a status check fails. The command still returns 0 overall. For example, if the public files directory is not writable, I see:

 [error]  The webserver needs to be able to write to the public files directory (public://). Please check your server configuration and try again. 

No update hooks are run after this message. When I comment out the failing status check, update hooks appear and run fine. For context, this is during an 8.3 => 8.4 update.

@weitzman
Copy link
Member

weitzman commented Jan 18, 2018

I would like to see an option which controls whether to fail on status checks. the option should default to false. if the option is false, false, updates should run.

@pfrenssen
Copy link
Member

pfrenssen commented Jan 19, 2018

Something like --stop-on-failed-status-check?

We could also do the opposite, --skip-status-check or --ignore-status-check.

@weitzman
Copy link
Member

Fixed by a confirmation prompt asking user "Requirements error found. Do you wish to proceed"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants