Running the core upgrade tool in a browser to migrate a D7 site to D8.

The migration failed. Migration tool reported only that content type migrations (article, page, etc) failed because requirements were not met. One of the several missing requirements described in the log was "d7 user requirement not met" or some such.

Long time later, found that total imported users stopped short. Found the very next row in the original user list was missing the user email value. This site has spent time as D4, D5, D6, and D7 in the last 15 years - your guess is as good as mine.

Inserted a dummy email email address into the original table for this user and the next migration attempt executed without error.

Would have been nice to throw up an error message like "incomplete user account info" or something.

Thought I would write it up for the future.

Comments

seaneffel created an issue. See original summary.

seaneffel’s picture

seaneffel commented
Title: D8 upgrade fails silently if any user account has blank email field » Empty email field breaks user migration

Just a smarter title

Version: 8.7.10 » 8.7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 8.7.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
quietone’s picture

quietone commented
Status: Active » Closed (cannot reproduce)
Issue tags: +Bug Smash Initiative

@seaneffel, thanks for the bug report.

I tested this on 10.0.x and was not able to reproduce this error. I deleted the email address for a user in the D7 test fixture that also was the author of two nodes. Then, starting from a fresh standard install I ran a migration from the UI, /upgrade. There were no error message about the user not migrating and the nodes that the user authored were correct and editable.

Therefore, closing as cannot reproduce. If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue (starting from "Install Drupal core").

Thanks!