-
Notifications
You must be signed in to change notification settings - Fork 74
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
Experiences upgrading to 22.05 #165
Comments
22.05 is neither released nor supported by this role yet :( We really do not advise doing this just yet.
yep, the docs aren't written yet because 22.05 is not released. You're very brave/adventurous to try it! Personally I will be staying on 22.01 at least for a little while longer until we have a good migration path,. |
Might be worth considering being more explicit about which versions are supported? The "New options for Galaxy 22.01 and later"section in the README seems to imply later versions are supported, particularly since 22.05 is mentioned. |
A "this role supports versions X through Y" would definitely be good, although FWIW we do commit to making sure it supports the latest released version before the release is officially released. |
Hi there, |
I think this is all solved at this point and everything fairly recent is supported. |
I just wanted to document some experiences I had when upgrading to 22.05 with an Ansible installation. Hopefully this will help others who are planning to do the same thing.
requirements.txt
, then figure out command to use to perform the update (ansible-galaxy install -p roles -r requirements.yml --force
)galaxyserver.yml
needed to be changed to remove theuwsgi
section and add agravity
section. I subsequently discovered that theuwsgi
was not removed from the installed configuration file, which caused some confusion when Galaxy failed to start (I thought it may have been caused by these entries.)nginx
template had to be modified to supportgunicorn
At this point, Galaxy failed to start. The main log file no longer seemed to have useful information to debug this. It was not obvious where to look as log files now split over different locations. I eventually found the log files in
/srv/galaxy/var/gravity/log
.In the end, I was able to find the following issues:
/srv/galaxy/var/gravity/supervisor/*
(owner/group root instead of galaxy)/srv/galaxy/var/gravity/supervisor/supervisor.sock
The new galaxyctl command looks great, but it is not clear how to use it in this environment.
Good luck!
The text was updated successfully, but these errors were encountered: