Overview

During the upgrade process from v5 to v7, you encounter a field called 'Failed App Master Behavior' and may be unsure of its function. You wish to keep both their old and new instances running simultaneously without deleting or detaching the old instance. Further into the upgrade process, you encounter errors such as 'No such cookbook: redis' and 'HTTPServerException: 412 Precondition Failed'. Even after making the required changes, errors are experienced with Chef, specifically a failure in starting the redis-server service.

Solution

To resolve the issue experienced during the upgrade process from v5 to v7, follow these steps:

1. Correct the entries in your '/etc/chef/recipes/cookbooks/custom-redis'. The correct recipe in ey-cookbooks-stable-v7 is 'ey-redis', not 'redis'. Make sure to replace all instances of 'redis' with 'ey-redis' in your custom-redis cookbook.
2. If you're still experiencing errors with the chef, specifically a failure in starting the redis-server service, consider disabling the 'custom-redis' recipe.
3. Set the environment variable 'EY_REDIS_ENABLED' as true. This can be done instead of using the recipe and should improve your environment's usability.

Summary

Upgrading from v5 to v7 can present some challenges, but by correcting the entries in your custom-redis cookbook, disabling the custom-redis recipe if necessary, and setting the EY_REDIS_ENABLED environment variable to true, you should be able to successfully complete the upgrade process.

FAQ

• Can I keep both my old and new instances running simultaneously without deleting or detaching the old instance?
  Yes, you can keep both instances running simultaneously. However, ensure that your configurations are correct to avoid conflicts.