Support #22436
closed
Remove `arvados-server install`, `arvados-package`
Description
Both of these features were prototypes to simplify the install process. They never got developed far enough to become fully supported processes, and at this point, we would rather invest our efforts into Ansible playbooks.
Remove both these features. arvados-package was purely an internal tool so it can go away wholesale. It might be a nice affordance if arvados-server install pointed you to documentation with newer methods, and then exited with an error.
Don't forget to remove arvados-package test and build stuff from the build directory.
arvbox note¶
Arvbox is using arvados-server install so we either need to make Arvbox use Ansible or replace arvbox altogether (#22580)
Updated by Peter Amstutz about 1 year ago
- Target version changed from Development 2025-01-29 to Development 2025-02-12
Updated by Peter Amstutz about 1 year ago
- Target version changed from Development 2025-02-12 to Development 2025-02-26
Updated by Brett Smith about 1 year ago
Arvbox is using
arvados-server installso we either need to make Arvbox use Ansible or replace arvbox altogether (#22580)
Given this requirement it doesn't make sense to have this ticket on this sprint. We should handle arvbox first, then come back to this.
Updated by Peter Amstutz about 1 year ago
- Target version changed from Development 2025-02-26 to Development 2025-03-19
Updated by Peter Amstutz about 1 year ago
- Target version changed from Development 2025-03-19 to Development 2025-04-02
Updated by Peter Amstutz about 1 year ago
- Target version changed from Development 2025-04-02 to Development 2025-04-30
Updated by Brett Smith 10 months ago
- Has duplicate Feature #22490: Remove `arvados-server install` added
Updated by Brett Smith 9 months ago
- Release set to 79
- Target version deleted (
Future)
Updated by Brett Smith 9 months ago
- Blocked by Support #23012: Remove arvbox added
Updated by Brett Smith 8 months ago
- Related to Bug #20723: Stop running setup.py in our build+test infrastructure (will be deprecated by Oct 31st 2025) added
Updated by Brett Smith 8 months ago
arvados-package was removed as part of #20311 in 69e00a3c231b58133d1b986397bba25986e29689. arvados-server install is all that's left and still blocked on an alternative arvbox testing strategy. (Which we've made progress on but still need to get across the finish line.)
Updated by Brett Smith 7 months ago
- Blocked by Feature #23115: Build Workbench development Docker image with Ansible added
Updated by Brett Smith 6 months ago
- Target version set to Development 2025-10-15
Updated by Brett Smith 6 months ago
- Target version deleted (
Development 2025-10-15)
Updated by Brett Smith 5 months ago
- Target version set to Development 2025-10-29
Updated by Brett Smith 5 months ago
- Status changed from New to In Progress
22436-drop-components @ 94647edbc2a67bf87d75a92279e3ed25bdcb6918 - developer-run-tests: #4912 (failing test is #22997)
- All agreed upon points are implemented / addressed. Describe changes from pre-implementation design.
- Yes and
- removed a lot of explicit references to
/var/lib/arvadosthat were implicitly expecting to run afterarvados-server install. - Discovered
arv-federation-migrate. Its last test run was almost five years ago. Removed the test and moved the script toarvados-bootstrapwhere it both makes more sense and reflects the level of support we give it. - Cleaned up other loose things I found that ideally would've been handled in other tickets but didn't get caught.
- Anything not implemented (discovered or discussed during work) has a follow-up story.
- #23225 - This test is already not running in Jenkins and that's been true for a while. Fixing this can be a post-release thing since it's "just" a test and will probably require a rebuild of the Jenkins worker node.
- Code is tested and passing, both automated and manual, what manual testing was done is described.
- See above
- Tested code incorporates recent main branch changes.
- Yes
- New or changed UI/UX and has gotten feedback from stakeholders.
- N/A
- Documentation has been updated.
- Wrote upgrade notes
- Behaves appropriately at the intended scale (describe intended scale).
- No change in scale
- Considered backwards and forwards compatibility issues between client and server.
- Everything we're dropping has been discussed and agreed
- Follows our coding standards and GUI style guidelines.
- Yes
Updated by Tom Clegg 5 months ago
LGTM. Only issue I see is that indentation went wrong in rpm-*) in run-library.sh → package_go_binary() (due to a prevailing mix of 2- and 4-space indent)
case "$package_format-$TARGET" in
# Red Hat-based distributions do not support native cross compilation at
# all (they use a qemu-based solution we haven't implemented yet).
rpm-*)
cross_compilation=0
Updated by Brett Smith 5 months ago
After this merged yesterday, there were some unrelated Rocky package build failures where the mirrors were inaccessible (because of us-east-1?), but it eventually cleared and we got all the way through the build pipeline at diagnostics-tordo: #1387
Updated by Brett Smith 5 months ago
- Status changed from In Progress to Resolved