Skip to content
This repository has been archived by the owner on Nov 12, 2024. It is now read-only.

[18.09] fix cvmfs install #220

Merged
merged 4 commits into from
Dec 12, 2018
Merged

[18.09] fix cvmfs install #220

merged 4 commits into from
Dec 12, 2018

Conversation

abretaud
Copy link
Contributor

I'm trying to fix errors in the galaxy docker compose images (a PR should come soon).
I found this problem with apt install of cvmfs, I think the key needs to be installed before adding the apt repo

@drosofff
Copy link
Member

Hi Anthony,

I profit from the occasion, to propose that the ansible version is "pinned" and the same for all galaxyproject-ansible repositories.
I am not saying that it is your issue, but I suspect pip install ansible without == in the .travis.yml is a possible option.
On the same line I am currently investigating why the last PRs of ansible-galaxy-os are not compatible with GalaxyKickStart and I suspect similarly that this is a problem of ansible syntaxe.

Cheers

@bgruening
Copy link
Member

bgruening commented Dec 12, 2018

@drosofff ansible is really changing fast. I agree we should document the tested ansbile versions of our roles and test those. Good project for next year or maybe Xmas :)

@drosofff
Copy link
Member

@bgruening

Good project for next year or maybe Xmas :)

Definitely for the next year, IntergalacticAnsible Utilities Commission IAUC ;-) I'd love !
For Xmas, I have unfortunately already several good projects waiting in the queue :-/

@bgruening
Copy link
Member

I will get this in, we can fix the failure in the branch or when we merge the branch back to master.

Thanks @abretaud!

@bgruening bgruening merged commit 5c240b9 into galaxyproject:18.09 Dec 12, 2018
@bgruening
Copy link
Member

@drosofff that was more a note to myself :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants