Task #5638: ansible-pulp on EL7 should use postgres 10 SCL rather than 9.6 SCL - Pulp

Actions

Send by e-mail Copy link

Task #5638

closed

ansible-pulp on EL7 should use postgres 10 SCL rather than 9.6 SCL

Added by mdepaulo@redhat.com over 4 years ago. Updated over 2 years ago.

Status:

CLOSED - WONTFIX

Priority:

Normal

Assignee:

Category:

Installer - Moved to GitHub issues

Sprint/Milestone:

Start date:

Due date:

% Done:

100%

Estimated time:

(Total: 0:00 h)

Platform Release:

Groomed:

Sprint Candidate:

Yes

Tags:

CI/CD

Sprint:

Quarter:

Description

ansible-pulp, when run against RHEL7/CentOS 7, currently enables and uses the SCL for Postgres 9.6

It should use the SCL for Postgres 10 instead.

In addition to the benefits to Pulp itself of a newer database, the benefits are:
1. EOL on May 2021 rather than Oct 2020.
https://access.redhat.com/support/policy/updates/rhscl
2. Katello (currently integrating Pulp 3) wants to use Postgres 10 as well. (They are currenlty using an older 9.x). And they do not want 2 database instances running for 2 different versions of postgres.

The downsides to us doing this (which might be mitigated) are:
1. If we want to keep Postgres 9.6 support for a while, ansible-pulp's molecule CI would have to test it. molecule theoretically override the vars though for a new test config, but adding another test config for the 3 containers molecule phase (and thus 4 containers) would slow down CI a little (or a lot if low on RAM.)

Sub-issues 1 (0 open — 1 closed)