Issue #5327
closedpsql doesn't work on the pulp2-nightly-pulp3-source-centos7 box
Description
Pulp 3 functions fine, it's just postgresql client which doesn't work.
(pulp) [vagrant@pulp2-nightly-pulp3-source-centos7 ~]$ psql
psql: error while loading shared libraries: libpq.so.rh-postgresql96-5: cannot open shared object file: No such file or directory
Updated by amacdona@redhat.com over 5 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 57
Updated by ttereshc about 5 years ago
Creating a symlink to the expected location helped. I guess adding /opt/rh/rh-postgresql96/root/ to the path will also help. Though I'm surprised why installation doesn't create symlink in /usr/lib64. :/
sudo ln -s /opt/rh/rh-postgresql96/root/usr/lib64/libpq.so.rh-postgresql96-5 /usr/lib64/libpq.so.rh-postgresql96-5
Updated by dalley about 5 years ago
I don't think this is a bug per-se, it's just how SCLs work, since you can have multiple installed in parallel and to accommodate that you are forced to explicitly specify which version you want.
According to: https://www.softwarecollections.org/en/scls/rhscl/rh-postgresql96/
What we should do is
scl enable rh-postgresql96 -- psql
Since we are only using one version of the SCL, we could possibly set it up to be permanently enabled by adding it to the bashprofile.
https://serverfault.com/questions/751155/permanently-enable-a-scl
Updated by dalley about 5 years ago
- Status changed from NEW to POST
- Assignee set to dalley
Added by dalley about 5 years ago
Added by dalley about 5 years ago
Revision 98c55227 | View on GitHub
Automatically source the SCL when using CentOS
Make sure commands like psql work correctly.
Updated by dalley about 5 years ago
- Status changed from POST to MODIFIED
Applied in changeset ansible-pulp3|98c552274e462b1455c4396528f4533542600618.
Updated by bmbouter almost 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Automatically source the SCL when using CentOS
Make sure commands like psql work correctly.
closes: #5327 https://pulp.plan.io/issues/5327