search

ubccr / coldfront

HPC Resource Allocation System
https://coldfront.readthedocs.io
GNU General Public License v3.0
96 stars 76 forks source link

Version in the UI does not change after upgraded from 1.1.3 to 1.1.4 #508

Closed carvinch closed 1 year ago

carvinch commented 1 year ago

I upgrade coldfront from 1.1.3 to 1.1.4. In the backend, the coldfront version and database are all upgraded. I can see 7 new tables are added into the database. But from the UI, it still shows the version of 1.1.3.

carvinch commented 1 year ago

Solved , all works fine currently.

dsajdak commented 1 year ago

@carvinch I'm curious if you did anything else to make this work? We have others reporting similar issues with upgrading

carvinch commented 1 year ago

We create a new env by python39 in the same directory, and then upgrade in the new env, after that it works. The detail is as follows:

  1. The first time, we tried to upgrade directly, run the commands, as the guide, no error messages, but nothing new installed. Then we realized that our python version is not meet the requirement because django3.2.17 need python 3.8 or higher, so we upgrade the python from 3.6 to 3.9 and then tried another three times.
  2. The second time, we built a python39 virtual environment with the same name as python36 venv at the same directory, and then upgrade. The database migrated but in the UI it still showed 1.1.3. We found that It still used the site package of python36, even we set python39 as the current python version.
  3. The third time, we built a pythen39 virtual environment in a different name in the same installation directory, and then upgraded in the new virtual environment. This time we upgraded successfully.

  4. We also tried to upgrade the virtual environment to python39 first, and then did the upgrade. But the result is the same as in the second time, it still used the python36 site package even the python environment is python39.

    latest update: use method 4, reinstall gunicorn with force tag in the virtual environment, and then run sudo systemctl daemon-reload, restart gunicorn, the upgrade will success. We must install gunicorn manually in virtual environment after the previous steps, otherwise in lib64/python3.9 won't have gunicorn, and gunicorn will point to lib64/python3.6, that is why we see the old version after upgrade.