usegalaxy-no / galaxyadmin

A repository for managing the work of the usegalaxy.no GalaxyAdmin team
0 stars 0 forks source link

Upgrade to 21.05 checklist #47

Closed kjetilkl closed 3 years ago

kjetilkl commented 3 years ago

Release notes

Testing checklist

When you have performed a test, sign your name behind it. An item should only be checked off the list after a sufficient number of people have tested the same feature. Remember to use the test server for now! The production server will be updated later.

Updates to Galaxy configuration files

Updates to custom modified Galaxy files

Looks and auth

Links

Basic operations

New stuff v20.01

New stuff v20.09

New stuff v21.01

New stuff v21.05

kjetilkl commented 3 years ago

Some observations regarding the failed tests:

In order to import a history via a URL from another Galaxy server, the history has to be "made accessible" by selecting "Share or Publish" from the history context menu, or else you will get a "HTTP 403 Forbidden" error when trying to import.

The "Export a history to your personal DropBox account" failed with the following error:

Traceback (most recent call last):
  File "/data/part0/tmp/jobs/000/829/configs/tmp0hguwxtz", line 1, in <module>
    from galaxy.tools.imp_exp.export_history import main; main()
  File "/srv/galaxy/server/lib/galaxy/tools/__init__.py", line 195
    min_version: Union[packaging.version.LegacyVersion, packaging.version.Version]
               ^
SyntaxError: invalid syntax

My hypothesis is that this could be a problem with the Python version. It fails when the export job is executed on the (test) Slurm node, but it worked when I forced the job to run on the "local" node by adding the following line to the /srv/galaxy/dynamic_rules/usegalaxy/tool_destinations.yaml configuration file.

__EXPORT_HISTORY_TO_URI__: { runner: local }
kjetilkl commented 3 years ago

Regarding histories exported from UseGalaxy.no via URLs, these cannot be imported directly into other Galaxies using the link. The reason seems to be that UseGalaxy.no will redirect any client that does not have a valid Galaxy session to the login page. This also affects the current production server, so the problem is not related to the version upgrade. However, it only affects our server but works perfectly fine on EU and Main.