-
Notifications
You must be signed in to change notification settings - Fork 5
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
Upgrade Magento to 2.4.0 #425
Conversation
tkotosz
commented
Sep 25, 2020
•
edited
Loading
edited
Note:
|
site working fine now (note: 2FA enabled by default for admin!) |
|
correct, forgot to copy that over once I had a working environment. I will do that on monday, when I am back in the office. :) |
@kierenevans I have updated the config.php to the new version, hopefully this will fix the problem. :) |
services:
All service version looks good except the redis-session version, it seem that is still on 4.0 for some reason 🤔 update: oh I see why, the service is called redis-session, but the config is called redis_session 🤦 |
fix seems to be fine:
php: 7.4 |
@kierenevans btw I think redis and redis-session probably should use the same configuration for the image to make sure they are using the same version. What do you think? |
Got further, need to add Solves:
|
this error happens also if it didn't pickup the elasticsearch hostname from the env.php (or during install from the cli option). I will add the wait anyway, then we will see... |
https://github.com/inviqa/harness-base-php/blob/0.10.x/src/magento2/.ci/sample-dynamic/workspace.yml and https://github.com/inviqa/harness-base-php/blob/0.10.x/src/magento2/.ci/sample-static/workspace.yml are overriding the services list to test with varnish. |
haha thanks, I just spotted that as well 🤞 |
They could be backed by separate services in production (hosted redis rather than on the cluster), so could be different versions. |
ah I see... make sense |
I cannot reproduce the failing test issue (502). Tried with normal installation and in pipeline mode as well. 🤔 |
I managed to reproduce using a slightly modified When using varnish, console talks to console -> tls-offload -> varnish -> nginx -> php-fpm The increase of buffer size in nginx has led to this error in tls-offload:
So to fix, we need to increase the buffer size in tls-offload too. |
ahaa nice catch! I was trying to test with static mode (https://github.com/inviqa/harness-base-php#static-mode) that didn't help to discover the issue... I assume it can only be reproduced with the |
That should have worked too, but perhaps missing the environment variable for running the behat step? |
I did anyway with |