-
Notifications
You must be signed in to change notification settings - Fork 18
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
Bump omero_figure_release to 5.0.0 everywhere #362
Conversation
👍 Similar question as always with OMERO.figure: does the figure script need to be updated i.e. do we need a server restart in addition to the OMERO.web restart? |
Yes, the script does need updating. But I'm not familiar with how that happens on our playbooks (normally a script update wouldn't require a server restart) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The script updates are standalone tasks similar to
prod-playbooks/omero/ome-dundeeomero.yml
Lines 177 to 184 in 83513f1
- name: Download the Figure_To_Pdf.py script | |
become: yes | |
get_url: | |
url: https://raw.githubusercontent.com/ome/omero-figure/v{{ omero_figure_release }}/omero_figure/scripts/omero/figure_scripts/Figure_To_Pdf.py | |
dest: /opt/omero/server/OMERO.server/lib/scripts/omero/figure_scripts/Figure_To_Pdf.py | |
mode: 0644 | |
owner: root | |
force: yes |
omero_figure_release
variable that you modified already. So no additional change is required.
Looking at the tasks, you are correct a server restart is not required when this task is updated. This is useful and allows us to apply these upgrades without downtime
@pwalczysko any preference on how to proceed here for the deployment?
I know how to do the training servers, as the playbook is just one there for omero and web. Is it feasible to run just the web-related playbooks on ns ? (which ones exactly if yes ?) |
Practically, it's the same process as the server except you are running other playbooks with different scopes:
I expect you have full permissions to be able to run both playbooks. That being said, it would be very timely to confirm this is the case and fix issues if necessary. |
@sbesson Ran the two playbooks (from this branch) you mention in #362 (comment) against three servers in check mode:
The output looked reasonable and there were no probs with authentication |
I will hold on upgrading further servers until the problem with
When the attempt is made to export the pdf from the OMERO.figure UI on ome-training-4. Edit: Checked that
|
Thanks @pwalczysko, it looks like the replacement of the script file directly within the server directory is not sufficient and additional logic is required to update the internal checksums. Possibly previous OMERO.figure upgrades were combined with OMERO.server upgrades so that the service restart was triggered anyways and we did not encounter this error. Options I can think of:
|
As discussed this morning (@sbesson and @pwalczysko), plan for nightshade is to upgrade omero-web via the playbook. At the same time, update the figure script manually via |
Seb: might be due the fact So we resorted to replace script via playbook and a restart of the server. |
As @will-moore noted, the route of running the ansible playbook Atm, all the servers (4 outreach servers, demo, ns-private and ns-public) are upgraded and working as expected. |
Bump OMERO.figure version to latest 5.0.0 everywhere.
cc @pwalczysko