Project

General

Profile

Actions

Bug #19095

closed

Update singularity dependency to get loopback device fix

Added by Tom Clegg about 2 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
05/05/2022
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
-
Release relationship:
Auto

Subtasks 1 (0 open1 closed)

Task #19098: Review 19095-singularity-bugfixResolvedWard Vandewege05/05/2022

Actions

Related issues

Related to Arvados - Bug #19077: arvbox maintenanceResolvedPeter Amstutz

Actions
Related to Arvados - Support #18566: Document singularity loopback device conflict bugResolvedTom Clegg12/10/2021

Actions
Actions #1

Updated by Tom Clegg about 2 months ago

Actions #2

Updated by Tom Clegg about 2 months ago

  • Related to Support #18566: Document singularity loopback device conflict bug added
Actions #3

Updated by Tom Clegg about 2 months ago

  • Status changed from New to In Progress
Actions #4

Updated by Tom Clegg about 2 months ago

19095-singularity-bugfix @ 438c1957f41643650b9a54419179c9228cd6fa6c -- developer-run-tests: #3088

This also includes a commit adding rsync as a dev/test dependency in arvados-server install (it was previously a dependency only for package-building mode). This is needed for an unrelated issue #15370 but I figure it makes sense to get both changes into the next CI image build.

I removed the "if you get this error..." section from the docs, figuring web search for the error message will still turn up the suggested fix in the 2.4 docs.

Actions #5

Updated by Ward Vandewege about 2 months ago

Tom Clegg wrote:

19095-singularity-bugfix @ 438c1957f41643650b9a54419179c9228cd6fa6c -- developer-run-tests: #3088

This also includes a commit adding rsync as a dev/test dependency in arvados-server install (it was previously a dependency only for package-building mode). This is needed for an unrelated issue #15370 but I figure it makes sense to get both changes into the next CI image build.

I removed the "if you get this error..." section from the docs, figuring web search for the error message will still turn up the suggested fix in the 2.4 docs.

Just one small thing in doc/install/crunch2/install-compute-node-singularity.html.textile.liquid, the "Singularity installation instructions" link still points at the 3.7 version, that should probably get bumped to the 3.9 version of that url.

Other than that - do we need to check/confirm with our users that are/were on singularity 3.7.4 to make sure this bump in Arvados 2.5.0 will be ok?

Assuming that's all fine, LGTM.

Actions #6

Updated by Tom Clegg about 2 months ago

Ward Vandewege wrote:

Just one small thing in doc/install/crunch2/install-compute-node-singularity.html.textile.liquid, the "Singularity installation instructions" link still points at the 3.7 version, that should probably get bumped to the 3.9 version of that url.

Ha, I got as far as confirming that the corresponding 3.9 link works, but didn't actually make the edit. Fixed.

19095-singularity-bugfix @ e826bf5dcaf591b42d42f80cea6c63c04e3db8dd

Other than that - do we need to check/confirm with our users that are/were on singularity 3.7.4 to make sure this bump in Arvados 2.5.0 will be ok?

I'm not sure what you have in mind here. If someone is relying on our compute image build script to keep them back at 3.7.4 then they would be disappointed by this -- is that a thing? Is there a known/likely disadvantage to using the newer version?

One option would be to have "arvados-server install" use a more recent version like 3.9.9 so we have a chance to detect any incompatibilities and avoid getting stuck depending on an ancient version, but leave the compute image script back at 3.7.4 until we have more motivation to update / more evidence that the newer version is as stable...?

Actions #7

Updated by Ward Vandewege about 2 months ago

  • Release set to 47

Tom Clegg wrote:

Ward Vandewege wrote:

Just one small thing in doc/install/crunch2/install-compute-node-singularity.html.textile.liquid, the "Singularity installation instructions" link still points at the 3.7 version, that should probably get bumped to the 3.9 version of that url.

Ha, I got as far as confirming that the corresponding 3.9 link works, but didn't actually make the edit. Fixed.

19095-singularity-bugfix @ e826bf5dcaf591b42d42f80cea6c63c04e3db8dd

Other than that - do we need to check/confirm with our users that are/were on singularity 3.7.4 to make sure this bump in Arvados 2.5.0 will be ok?

I'm not sure what you have in mind here. If someone is relying on our compute image build script to keep them back at 3.7.4 then they would be disappointed by this -- is that a thing? Is there a known/likely disadvantage to using the newer version?

One option would be to have "arvados-server install" use a more recent version like 3.9.9 so we have a chance to detect any incompatibilities and avoid getting stuck depending on an ancient version, but leave the compute image script back at 3.7.4 until we have more motivation to update / more evidence that the newer version is as stable...?

Since there are no changes to our code, I think we just need to notify our users. This probably deserves a mention in the release notes for 2.5.0.

LGTM, thanks!

Actions #8

Updated by Tom Clegg about 2 months ago

  • Status changed from In Progress to Resolved
Actions #9

Updated by Peter Amstutz about 1 month ago

  • Release changed from 47 to 51
Actions

Also available in: Atom PDF