Skip to content
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

Closed
Tracked by #3618
jarrah42 opened this issue Jul 19, 2022 · 5 comments
Closed
Tracked by #3618

Experiences upgrading to 22.05 #165

jarrah42 opened this issue Jul 19, 2022 · 5 comments

Comments

@jarrah42
Copy link

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.

  • Ansible role versions needed to be updated. I had to find the new version and update requirements.txt, then figure out command to use to perform the update (ansible-galaxy install -p roles -r requirements.yml --force)
  • Next, galaxyserver.yml needed to be changed to remove the uwsgi section and add a gravity section. I subsequently discovered that the uwsgi 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.)
  • Our nginx template had to be modified to support gunicorn

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:

  • There was a permission problem on /srv/galaxy/var/gravity/supervisor/* (owner/group root instead of galaxy)
  • I had to manually remove /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!

@hexylena
Copy link
Member

hexylena commented Jul 19, 2022

22.05 is neither released nor supported by this role yet :( We really do not advise doing this just yet.

  1. Unfortunately for you, the supervisor permission problem was already known to us. Sorry everyone has to re-discover that!
  2. Yes, part of the switch to gravity/supervisor has meant that journalctl is now useless. We're discussing alternatives that will let us retain the systemd/journalctl benefits.

but it is not clear how to use it in this environment.

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,.

@jarrah42
Copy link
Author

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.

@natefoo
Copy link
Member

natefoo commented Jul 19, 2022

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.

@lldelisle
Copy link

Hi there,
Thanks @jarrah42 for your report.
Which version of galaxy the ansible role version 0.10.7 is covering?
Thanks

@mvdbeek
Copy link
Member

mvdbeek commented Feb 14, 2023

I think this is all solved at this point and everything fairly recent is supported.

@mvdbeek mvdbeek closed this as completed Feb 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants