Project

General

Profile

Actions

Bug #18191

closed

[doc] the compute node image doc does not take releases into account

Added by Ward Vandewege over 4 years ago. Updated 7 months ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Story points:
-
Release:
Release relationship:
Auto

Description

The page at https://doc.arvados.org/install/crunch2-cloud/install-compute-node.html is source based, and it does not take our releases into account. This means that by default, you get the bleeding edge/dev packages in your freshly baked compute image, which is not what you want.

Solution: either fix it by adding an explicit git checkout command (this would need to be autogenerated with the correct git branch, use an existing/new variable in the doc build scripts), or package the build script as a proper OS package, versioned like everything else.

Actions #1

Updated by Ward Vandewege over 4 years ago

  • Description updated (diff)
Actions #2

Updated by Peter Amstutz about 3 years ago

  • Release set to 60
Actions #3

Updated by Peter Amstutz about 2 years ago

  • Target version set to Future
Actions #4

Updated by Brett Smith 7 months ago

  • Target version deleted (Future)
  • Status changed from New to Closed

Ward Vandewege wrote:

The page at https://doc.arvados.org/install/crunch2-cloud/install-compute-node.html is source based, and it does not take our releases into account. This means that by default, you get the bleeding edge/dev packages in your freshly baked compute image, which is not what you want.

The current version at least tells you to get the right release branch, and even if you get main the Ansible playbook gets you the last released version by default, not development packages (that's a separate configuration you have to opt into).

Actions

Also available in: Atom PDF