Update error: The hostname is already registered.

So you are doing a full site reinstall and then importing from config? That sounds like a duplicate config issue.

Check that you don't have duplicate items in the config (and that you are importing config from the correct directory.)

For re-install, you might also need to use the 'config_installer' profile. (https://www.drupal.org/project/config_installer/)

The D8 version doesn't auto-install a default domain anymore, so I don't think it's a module issue.

Note also that a re-install is not an update, so the description of this issue is not correct.

Which alpha versions are you upgrading from and to?

We had to change the logic for generated IDs a long time ago (Oct 2017), and there isn't much to do except (possibly) editing your config files and re-importing.

See Drupal\domain\Entity::createDomainId() for the logic. See also #2908236: Domain ID may vary between 32-bit and 64-bit versions of PHP

However, you'll then have to update the node access table, which uses this data.

Essentially, you'll need a custom update function for dealing with this problem, because alpha-to-alpha updates aren't supported.

Yeah, that's going to catch the ID change. This code should work in an update hook:

$update = FALSE;
$storage = \Drupal::entityTypeManager()->getStorage('domain');
$domains = $storage->loadMultiple();
foreach ($domains as $domain) {
  $current_id = $domain->getDomainId();
  $new_id = $domain->createDomainId();
  if ($current_id != $new_id) {
    $domain->saveProperty('domain_id', $new_id);
    $update = TRUE;
  }
}
if ($update) {
  node_access_needs_rebuild();
}

I would do the following (while being able to restore from backup if this fails):

* Update the module
* Run database updates
* Export config
* In the UI, you will be prompted to rebuild node access. That process can take a while, and I don't know if it can be done via drush.

That should update the config so that it is created properly on a re-install.

Thinking through this issue, this patch might also fix it, though you would still be susceptible to the 32-bit / 64-bit issue.

Thanks for the test. I think we should add that code with a note about why it's there -- essentially, to prevent updating a domain id from a config file.

Thanks @agentrickard this helped

Hi @agentrickard,
is possible to release new version with this fix?

Thanks

Yes. I was trying to wait for https://www.drupal.org/project/domain/issues/3004243, but that's delayed.

It would be nice to get a review of #3025541: configFactory service invoking hooks early as well.