Install more recent versions of OMERO.py

[sbesson]

This relaxes the pinning of the OMERO.py version to allow the Prometheus exporter to keep connecting to OMERO.server instances with the latest security protocol enhancements. Without this change, the createSession() will fail Connection reset by peer and the metrics endpoint returns a Connection refused

This was discovered in the context of ome/omero-certificates#38 (review). After running the latest omero certificates command, the monitoring endpoint started failing for this instance. Locally, this got resolved by running

[sbesson@test120-omeroreadonly-2 prometheus-omero-tools]$ sudo /opt/prometheus-omero-tools/venv3/bin/pip install -U omero-py
[sbesson@test120-omeroreadonly-2 prometheus-omero-tools]$ sudo systemctl restart prometheus-omero-exporter

A patch release of the role will be required in order for the monitoring of next IDR deployments to remain functional with omero-certificates 0.3.0. Note also the Molecule CI is failing and might need to be fixed separately or as a prerequisite @pwalczysko and @khaledk2

[sbesson]

I think OMERO.py 5.13.0 is the minimal version required in order to connect against a server set-up with the latest omero-certificates and d882eda updates the role accordingly.
A secondary advantage of increasing the minimal version is that the new version of the role will also force an OMERO.py upgrade of existing deployments created with an older version of this role.

[pwalczysko]

Build is green on #10

[pwalczysko]

Maybe rebase to master to make build pass ? The #10 is merged now.

[pwalczysko]

The test is now failing, was not successful in trying to fix it. I think the service is not running.

[sbesson]

@pwalczysko I was also confused how your #10 ended up passing the builds while the actions on https://github.com/ome/prod-playbooks have been consistently failing since the release of omero-certificates 0.3.0.

After investigation, turns out the Molecule test was not setting up a server with self-signed certificates. 22a9e3a adds the corresponding option and fixes the CI build and 194789e adds a note to the README.

[pwalczysko]

Could we maybe merge this please ? I suppose merging it would fix the tests in ome/prod-playbooks#373 and thus allow the ome/prod-playbooks#373 to be merged. Or do I get it wrong ?

cc @sbesson @jburel

[sbesson]

Yes I believe this is the root issue of the failing monitoring tests. We'll also need this reviewed and released to consume it in the upcoming IDR deployments

[pwalczysko]

Yes I believe this is the root issue of the failing monitoring tests. We'll also need this reviewed and released to consume it in the upcoming IDR deployments

@sbesson Re-run the tests after this PR got merged, but still failing ome/prod-playbooks#373 - what am I getting wrong please ?

[sbesson]

Has this been released?

[jburel]

just tagged 0.3.4

[pwalczysko]

Run ome/action-ansible-galaxy-publish@main
  with:
    galaxy-api-key: ***
Run ansible-galaxy role import --api-key *** ${GITHUB_REPOSITORY%/*} ${GITHUB_REPOSITORY#*/}
  ansible-galaxy role import --api-key *** ${GITHUB_REPOSITORY%/*} ${GITHUB_REPOSITORY#*/}
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
ERROR! Error when finding available api versions from default (https://galaxy.ansible.com/) (HTTP Code: 403, Message: Forbidden)
Error: Process completed with exit code 1.

https://github.com/ome/ansible-role-omero-prometheus-exporter/actions/runs/6432255572/job/17467049347