-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
Support wsgi on python 3.8 and 3.9 on rhel8 #372
base: master
Are you sure you want to change the base?
Conversation
7637c1d
to
85347ac
Compare
0960831
to
85347ac
Compare
Hi @teluq-pbrideau, thanks for your contribution! I wanted to help as I have some experience with a similar thing from #370. Initially I pushed some changes directly to your branch - sorry for that! 😓 - but I reverted them now. I am doing my further experiments on it's copy, here #373. |
It seems to be a problem about upstream configuration about puppetdb itself. On my side, i’ve configured my infrastructure with package { 'postgresql-module':
ensure => '13',
name => 'postgresql',
enable_only => true,
provider => 'dnfmodule',
}
class { 'puppetdb::database::postgresql' :
listen_addresses => '0.0.0.0',
postgres_version => '10',
manage_package_repo => false,
manage_server => false,
database_password => $db_password.unwrap,
} as a weird hack that gets around installing correctly postgres Is the upstream puppetdb module run the acceptance test on centos successfully? |
(Yes, sorry @teluq-pbrideau, I moved your comment here.) |
No, but it's hard to tell why as the logs are gone, see https://github.com/puppetlabs/puppetlabs-puppetdb/actions/runs/2064063268 .... But it seems that the default installed Postgres version is 11 (https://github.com/puppetlabs/puppetlabs-puppetdb/blob/main/manifests/params.pp#L29), while this package does not seem to exist for Centos / Redhat 8 as both our Ci logs say:
|
Nevermind, just rebase from master, and test fail, I’ll work on them |
85347ac
to
d37799b
Compare
Only Ubuntu 18.04 is failing right now, which is an EOL OS, so you may remove support for that OS. |
@kenyon I’m not sure if it is the only place, I've found references on ubuntu 18.04 in |
6cdb569
to
14d52e6
Compare
Also, I see there is no acceptance test on RHEL (only on Debian and Ubuntu) and my PR is only related to RHEL. Would it be simple to include acceptance on Rocky also? I’ve never done these kind of tests, so not sure if I really want to go down this rabbit hole, but if it is simple to add Rocky to the mix, would you be willing to help me helping this community? |
14d52e6
to
faf08bc
Compare
I would like to but apparently I don't know how as I failed to fix the tests the last time I tried. @kenyon ? |
faf08bc
to
6557dff
Compare
I would rather have my changes merged than to wait another year for RHEL test to be included… Could we move forward please? |
6557dff
to
21c2699
Compare
3c0434c
to
8d7e907
Compare
8d7e907
to
15df7a6
Compare
Pull Request (PR) description
As inspired by issue mentioned, this fix the install of wsgi for python 3.8 and 3.9 on rhel.
There is no need to set to specific
mod_path
as the packages provides the file inhttpd/modules
I’m not a very confident test writer, but I did my best to test the changes I made. Please suggest what could be done better if you think it is required.
This Pull Request (PR) fixes the following issues
Fixes #369