-
-
Notifications
You must be signed in to change notification settings - Fork 370
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
Could not enable "PowerTools repository" on RHEL8 #298
Comments
Hello @SomeAverageDev
This repository is required to install dependencies for the
In our case, maybe you just need to comment out this task. I, in turn, will add variables to be able to choose (add repositories or not). |
Hello, RHEL recommandation is to enable the related repo: I don't think it is necessary at all on RHEL8 for this use case... I did not find any dependency in my "type A" installation |
It is possible that all the necessary dependencies for the postgresql-devel package are already present in the main repository and indeed the rest of the repositories are no longer needed. There was an error earlier because there were no dependent packages. Have you tried testing without installing these repositories? Unfortunately, I don't have an RHEL subscription to run the tests. Instead, I use CentOS/RockLinux for tests. |
For RHEL based distributions, the tests are successful (with PowerTools repository):
|
Hi, Same problem here:
And I have commented the postgres line in vars/RedHat.yml like this: postgresql_packages:
Would you be so kind to point me in the right direction? Thank you very much! (And thx for the superb playbook: it rocks!) P.S. If I substitute the correspondent line with subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms - as SomeAverageDev suggested - all works fine. |
Fix here #443 |
Hello,
First, thank you for this great playbook !
I have an issue while running the latest playbook version, on repositories tasks.
The power tools repo is not declared on the RHEL8 server (we are using internal Satellite, it could come from that also, I will try to check with my colleagues)
Please find the task log below:
This repo does not look necessary though in my installation context... don't really know if I need it.
The text was updated successfully, but these errors were encountered: