UCL-MIRSG / ansible-collection-infra

Ansible Collection to configure infrastructure for XNAT and OMERO
BSD 3-Clause "New" or "Revised" License
1 stars 1 forks source link

Fix issue with Container Service 3.6.0 update #140

Open HChughtai opened 1 month ago

HChughtai commented 1 month ago

Short Description

Integration test is failing when trying to update Container Service

Evidence/Steps to Reproduce

Acceptance Criteria/Expected Behaviour

Details

No response

Resolution

No response

HChughtai commented 1 month ago

I've tried running the molecule tests for the install xnat playbook locally, but keep hitting general network issues when downloading components. So didn't even get to the failure encountered via GH actions - e.g. this one.

HChughtai commented 1 month ago

This may be a similar issue: https://groups.google.com/g/xnat_discussion/c/yJZYYkEdchg/m/84y707MCAwAJ

p-j-smith commented 5 days ago

I think the original issue was due to incompatibility between plugins with the latest version of XNAT. If we deploy only the Container Service and Batch Launch plugins, we're still unable to add a docker host but the error we get is different.

I've opened a discussion on the forum to see if the developers have any ideas what the issue is.

p-j-smith commented 4 days ago

We will need to switch the container service host to use tcp rather than https. However, this currently leads to a different issue when using TLS (the container service doesn't set DOCKER_TLS_VERIFY so it tries to connect via HTTP instead of HTTPS). Looks like we have two options for now:

  1. don't use TLS on our Docker host
  2. wait for the Container Service to be patched and a new release made