Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rocky 8.7 and possibly-broken Ansible #263

Closed
donsizemore opened this issue Nov 15, 2022 · 2 comments
Closed

Rocky 8.7 and possibly-broken Ansible #263

donsizemore opened this issue Nov 15, 2022 · 2 comments

Comments

@donsizemore
Copy link
Member

Looks like the AWS Rocky image found the 8.7 update:
nothing provides (ansible-core >= 2.12.2 with ansible-core < 2.13) needed by ansible-5.4.0-3.el8.noarch

Apparently ansible as an OS package has been deprecated for some time; perhaps it's finally removed. Indeed, I don't see it at https://distro.ibiblio.org/rocky/8.7/AppStream/x86_64/os/Packages/a/

The recommended way to install Ansible is pip, so perhaps it's time to make that jump at https://github.com/GlobalDataverseCommunityConsortium/dataverse-ansible/blob/develop/ec2/ec2-create-instance.sh#L239 or kick the can and switch to ansible-core

@donsizemore
Copy link
Member Author

The current Vagrantfile seems to be broken, as well:

dnf -y --enablerepo=epel install ansible
<snip>
Error: 
 Problem: conflicting requests
  - nothing provides (ansible-core >= 2.12.2 with ansible-core < 2.13) needed by ansible-5.4.0-3.el8.noarch

@donsizemore
Copy link
Member Author

This was fixed with the release of the ansible-6.0 meta-package. Would still be nice to switch to pip, though.

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

No branches or pull requests

1 participant