Non-existent service "queue.redis" error

drush -y si

 You are about to:
 * DROP all tables in your 'drupal' database.

 // Do you want to continue?: yes.                                                                                      

 [notice] Starting Drupal installation. This takes a while.
 [notice] Performed install task: install_select_language
 [notice] Performed install task: install_select_profile
 [notice] Performed install task: install_load_profile
 [notice] Performed install task: install_verify_requirements
 [notice] Performed install task: install_verify_database_ready
 [notice] Performed install task: install_base_system
 [notice] Performed install task: install_bootstrap_full
 [notice] Performed install task: install_profile_modules
 [notice] Performed install task: install_profile_themes
 [notice] Performed install task: install_install_profile

In ContainerBuilder.php line 1030:
                                                            
  You have requested a non-existent service "queue.redis".

changed the description

added To Do label

assigned to @jurgenhaas

added Doing label and removed To Do label

The problem is caused by the fact that we now configure Redis also for the development environment, as that improves performance significantly. That's achieved by adding these lines to settings.local.php:

$settings['redis.connection']['interface'] = 'PhpRedis';
$settings['redis.connection']['host'] = 'redis';
$settings['cache']['default'] = 'cache.backend.redis';
$settings['container_yamls'][] = 'modules/redis/example.services.yml';
$settings['queue_default'] = 'queue.redis';

Unfortunately, that requires the Redis module to be installed. Otherwise, that doesn't work and causes the above error message. When using an installation profile that also includes Redis, so that this will be enabled during the drush si process, then this doesn't happen. But when that Redis won't be enabled during initial site installation, this is a problem.

I'll have a look how we can prevent this from happening even in those rare cases.

mentioned in commit docker/gitlab-drupal-ci@38c7f074

mentioned in commit composer/plugin/drupal-environment@cb37e240

mentioned in commit docker/l3d@99033b37

This is now resolved with these new updates:

• L3D version 2.5.7
• Composer package drupal-environment version 3.0.21

The way it works:

The settings.local.php now contains this:

if (!getenv('L3D_DISABLE_REDIS') && file_exists('modules/contrib/redis/example.services.yml')) {
  $settings['redis.connection']['interface'] = 'PhpRedis';
  $settings['redis.connection']['host'] = 'redis';
  $settings['cache']['default'] = 'cache.backend.redis';
  $settings['container_yamls'][] = 'modules/contrib/redis/example.services.yml';
  $settings['queue_default'] = 'queue.redis';
}

That means, the Redis settings only get applied when the env variable L3D_DISABLE_REDIS is not set and if the redis services yaml file exists.

In addition to that, Drush in the latest L3D versions checks, if the command to install a new site is being executed and then sets that env variable and after the site installation automatically also installs Redis.

For installations where Redis should not be used at all, the following can be added to .lakedrops.yml:

docker4drupal:
  docker-compose.yml:
    services:
      php:
        environment:
          PHP_FPM_CLEAR_ENV: no
          L3D_DISABLE_REDIS: yes

This does not work after updating to L3D version 2.5.7 and drupal-environment version 3.0.21:

richard@af-grp-l3d:/drupal$ web/profiles/contrib/xyz/scripts/install/abc.sh grp rp demo no rp no

 You are about to:
 * DROP all tables in your 'drupal' database.

 // Do you want to continue?: yes.                                                                                      

 [notice] Starting Drupal installation. This takes a while.

In CheckExceptionOnInvalidReferenceBehaviorPass.php line 86:
                                                                                                             
  The service "cache_tags.invalidator.checksum" has a dependency on a non-existent service "redis.factory".  

If I set L3D_DISABLE_REDIS: 'yes' in .lakedrops.yml, then it works.

Yes, this is currently built to look for the site install keyword at position number 1 for the Drush command. In the script used above, the command is drush -y site:install ... i.e. the keyword is at position 2 and not 1. I need to find a more clever way to find out which drush command is being executed.

@richardpapp L3D v2.5.8 fixes this

closed

removed Doing label

reopened

added Doing label

mentioned in commit docker/gitlab-drupal-ci@66e32444

mentioned in commit docker/l3d@12055132

closed

removed Doing label

mentioned in commit devops-tools/documentation@4882005d