Arvados

22957-ansible-package-tests @ ff946732fcf7a6dfb85f9fd5f7486d76fd4d99ca

• All agreed upon points are implemented / addressed. Describe changes from pre-implementation design.
  • Yes
• Anything not implemented (discovered or discussed during work) has a follow-up story.
  • See below
• Code is tested and passing, both automated and manual, what manual testing was done is described.
  • For now I have manually tested by building and testing packages on both ubuntu2204 and rocky9. This covers both Debian and Red Hat, and an older and newer distribution. I can't test on Jenkins right now because, basically, I will need to build a new Jenkins test image with changes in this branch. So you should at least look at it and make sure you're roughly okay with it before we do automated testing. If you are, then next steps are:
    1. Update arvados-dev/ansible to remove the old ci_ansible role and use the new arvados_ansible role instead. The old role can be removed completely from the tests node playbook, because the new one will be run as part of install-test-env.yml instead.
    2. Build a new node from the branch.
    3. Run a package build+test from the branch on the new node. If this passes then we're good.
• New or changed UI/UX and has gotten feedback from stakeholders.
  • N/A
• Documentation has been updated.
  • Yes
  • Note I have not updated the Ansible install instructions for building a compute node. That is okay because for now the old instructions will still work. I would like to get farther, and at least do #22958, before we update those instructions. This is early enough I'm worried that there might be more churn with further development. I don't want to rewrite docs only to rewrite them again next branch.
• Behaves appropriately at the intended scale (describe intended scale).
  • This will probably run slower than the Dockerfile builds, but we're intentionally making that trade for code deduplication.
• Considered backwards and forwards compatibility issues between client and server.
  • N/A, pure build change
• Follows our coding standards and GUI style guidelines.
  • N/A, no Ansible style guide

Very interesting read. I did a test run on my side to see how it went with Ubuntu 24.04, all good.

LGTM, thanks

packer-build-jenkins-image-arvados-tests: #123

developer-run-tests: #4802 - Failed only on the "cannot mmap empty file" issue, looks good

build-packages-rocky9: #2 - Confirmed you can see the output from Ansible building the test Docker image

I'm not going to run any other build-packages jobs because of #22858 but I'm calling this good.