Story #6913: As a user, I can specify LD_LIBRARY_PATH for the pulpcore-api service - Pulp

Actions

Send by e-mail Copy link

Story #6913

closed

As a user, I can specify LD_LIBRARY_PATH for the pulpcore-api service

Added by spredzy almost 4 years ago. Updated almost 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

Category:

Installer - Moved to GitHub issues

Sprint/Milestone:

3.5.0

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Sprint Candidate:

Tags:

Sprint:

Sprint 74

Quarter:

Description

When using SCL, per its pattern, the LD_LIBRARY_PATH needs to be
specified in order for the libraries/binariess to find the "right"
version.

The scripts dropped in /etc/profile.d are working for login shells
but tasks we are running are using the pulp user which has no login
shell (/sbin/nologin).

Given rh-postgresql96 is currently used (and postgresql-devel-9.2)
gets installed during installation the lack of explicitly specifying it
might have gone un-noticed.

But when dealing with replacing rh-postgresql96 by rh-postgresql10
(and all related files) or simply installing the
rh-postgresql10-postgresql-libs and rh-postgresql10-postgresql-devel to connect to a PG10 server setup else where it fails with the following errors:

django.db.utils.OperationalError: SCRAM authentication requires libpq version 10 or above
/opt/rh/rh-postgresql10/root/bin/initdb: error while loading shared
libraries: libpq.so.rh-postgresql10-5: cannot open shared object
file: No such file or directory

Actions

Copy link

Updated by ipanova@redhat.com almost 4 years ago

Status changed from NEW to POST
Triaged changed from No to Yes
Sprint set to Sprint 74

https://github.com/pulp/pulp_installer/pull/319

Added by spredzy almost 4 years ago

Revision 9c29972b | View on GitHub

LD_LIBRARY_PATH: Allow one to specify a specific path

When using SCL, per its pattern, the LD_LIBRARY_PATH needs to be specified in order for the libraries/binariess to find the "right" version.

The scripts dropped in /etc/profile.d are working for login shells but tasks we are running are using the pulp user which has no login shell (/sbin/nologin).

Given rh-postgresql96 is currently used (and postgresql-devel-9.2) gets installed during installation the lack of explicitly specifying it might have gone un-noticed.

But when dealing with replacing rh-postgresql96 by rh-postgresql10 (and all related files) or simply installing the rh-postgresql10-postgresql-libs and rh-postgresql10-postgresql-devel to connect to a PG10 server setup else where it fails with the following errors:

django.db.utils.OperationalError: SCRAM authentication requires libpq version 10 or above
/opt/rh/rh-postgresql10/root/bin/initdb: error while loading shared libraries: libpq.so.rh-postgresql10-5: cannot open shared object file: No such file or directory

fixes #6913

Added by spredzy almost 4 years ago

Revision 9c29972b | View on GitHub

LD_LIBRARY_PATH: Allow one to specify a specific path

When using SCL, per its pattern, the LD_LIBRARY_PATH needs to be specified in order for the libraries/binariess to find the "right" version.

The scripts dropped in /etc/profile.d are working for login shells but tasks we are running are using the pulp user which has no login shell (/sbin/nologin).

Given rh-postgresql96 is currently used (and postgresql-devel-9.2) gets installed during installation the lack of explicitly specifying it might have gone un-noticed.

But when dealing with replacing rh-postgresql96 by rh-postgresql10 (and all related files) or simply installing the rh-postgresql10-postgresql-libs and rh-postgresql10-postgresql-devel to connect to a PG10 server setup else where it fails with the following errors:

django.db.utils.OperationalError: SCRAM authentication requires libpq version 10 or above
/opt/rh/rh-postgresql10/root/bin/initdb: error while loading shared libraries: libpq.so.rh-postgresql10-5: cannot open shared object file: No such file or directory

fixes #6913

Actions

Copy link

Updated by spredzy almost 4 years ago

Status changed from POST to MODIFIED

Applied in changeset ansible-pulp|9c29972b23f939833b9f0b5a787f3b72a6a8eb65.

Actions

Copy link

Updated by mdepaulo@redhat.com almost 4 years ago

Tracker changed from Issue to Story
Subject changed from LD_LIBRARY_PATH not properly specified and no way to specify it to As a user, I can specify LD_LIBRARY_PATH for the pulpcore-api service
% Done set to 0

Updating from issue to "story", since this seems more like a feature (compatibility with additional IT environments.)

The commit/PR was already merged, but I will submit a new one to update the changelog entry from "misc" to "feature".