Issue #5079
closed
Installation in travis fails from time to time
Description
It seems like pulp_rpm playbook is not available for some reason, maybe not downloaded? timeout?
Restarting a job helps, not necessarily right away but eventually it will successfully pass this installation step.
# Run Ansible playbook
cd ../ansible-pulp
ansible-galaxy install -r requirements.yml
- extracting geerlingguy.postgresql to /home/travis/.ansible/roles/geerlingguy.postgresql
- geerlingguy.postgresql (master) was installed successfully
ansible-playbook --connection=local --inventory 127.0.0.1, playbook.yml --extra-vars \
"pulp_python_interpreter=$VIRTUAL_ENV/bin/python, pulp_install_dir=$VIRTUAL_ENV \
pulp_db_type=$DB"
ERROR! the role 'pulp.pulp_rpm_prerequisites' was not found in /home/travis/build/pulp/ansible-pulp/roles:/home/travis/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/home/travis/build/pulp/ansible-pulp
The error appears to be in '/home/travis/build/pulp/ansible-pulp/playbook.yml': line 30, column 7, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
roles:
- pulp.pulp_rpm_prerequisites
^ here
The command ".travis/install.sh" failed and exited with 1 during
Updated by dkliban@redhat.com over 5 years ago
Looks like github.com sometimes returns a 500 error when ansible tries to download the role from https://github.com/pulp/pulp-rpm-prerequisites/archive/master.tar.gz
The Travis build should fail at this point and not go forward.
Updated by ggainey over 5 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 56
Updated by mdepaulo@redhat.com over 5 years ago
- Status changed from NEW to CLOSED - CURRENTRELEASE
- Assignee set to mdepaulo@redhat.com
This is now fixed for pulp_rpm by 2 different changes; each fixes it on its own:
1. .travis/install.sh now has "set -euv" at the beginning thanks to a change someone else made to plugin-template. This means that said failed command (rc 1) would cause a Travis build error.
2. Said ansible command no longer gets run; instead we use containers. (Technically ansible is used to wrap around the container build commands, but it does not download ansible roles from the internet.)
.