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

edb-ansible roles/tasks using pg_version variable does not function with RHEL8 appstream repository with enable_edb_repo=false #592

Open
Lyuven opened this issue Sep 19, 2023 · 1 comment

Comments

@Lyuven
Copy link

Lyuven commented Sep 19, 2023

Hi! This issue might be a bit too specific to apply fixes, but I think it should at least be known:

Red Hat uses Appstream/module solution* which omits the version number in the package name (for example postgresql15-server becomes only postgresql-server in RHEL8 appstream repo). Every role/task that mentions pg_version will automatically fail due to naming conflict where role/task is attempting to [for example] install postgresql15-server when it should be looking for postgresql-server (while enabling v15 like this: yum module enable postgresql-server:15).

This becomes an issue when you set enable_edb_repo=false and you're in an offline environment with restricted access to repositories other than official RHEL8 repositories.

One solution could be to set the pg_version to null which should effectively append nothing while having a secondary variable something like: pg_module_version applied to where-conditions where you want to check version of PG without appending to reponames. Otherwise it might be wise to include an appendix at supported distributions that RHEL >=8 requires external repositories.

Regards,
Lyuven

@Lyuven Lyuven changed the title edb-ansible collection does not function with RHEL8 appstream repository with enable_edb_repo=false edb-ansible roles/tasks using pg_version variable does not function with RHEL8 appstream repository with enable_edb_repo=false Sep 19, 2023
@hannahms
Copy link
Collaborator

Hi there,

Thank you for pointing this out. I will update the documentation as suggested and look into the suggested updates and ensure the package naming convention is followed for various repositories and use-cases.

Regards,
Hannah

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

2 participants