Arvados

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.

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.

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