-
Notifications
You must be signed in to change notification settings - Fork 105
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
Minor version upgrade #118
Comments
Hi @BelCo94 , sorry for the late reply, I will try to look at this soon. |
@BelCo94 I can confirm the bug, looking into it. |
@BelCo94 fixed now, I will push again 6.0.40 images, but as the fix is present in this version onwards, upgrades from a previous version like 6.0.38 will need to be done manually as you did. |
@juanluisbaptiste Did you push that to anywhere? Seems the images 6.0.37 and 6.0.40 still have this error.
(sorry for that confusion, this is not actually needed) Ps. Oh no!
seems this is the only image this has been fixed |
While testing issue #123 I found that previous fix was wrong, and it ended up overwriting the contents of |
Sorry for the noise, I did some commit rebasing last night, I wasn't aware that these messages were going to be added again. |
Files and modules are not upgraded when minor version upgrading, according to the instructions from README.md.
Image versions: 6.0.37 and 6.0.38
Upgrade is successful only if I manually create a file "current_version" in volume mounted to
/opt/otrs/Kernel/
and put information about current version in it (6.0.37). After upgrade file contains new version (6.0.38).I think the problem is the file "current_version" is being created and checked in different places by function
load_defaults()
inotrs/functions.sh
:line 254:
local current_version_file="${OTRS_CONFIG_DIR}/current_version"
line 273:
echo ${current_version} > ${OTRS_ROOT}/current_version
docker-compose.yml
.env
logs
The text was updated successfully, but these errors were encountered: