Bug 1201389
Summary: | condor-python package installs libpyclassad to the wrong place | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Matt Williams <matt> | ||||
Component: | condor | Assignee: | matt | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 21 | CC: | abakrim5, bbockelm, eerlands, matt, tomspur, tstclair | ||||
Target Milestone: | --- | Keywords: | Reopened | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | condor-8.3.8-1.fc23 condor-8.5.0-1.fc21 condor-8.5.0-1.fc22 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-10-26 13:19:28 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Matt Williams
2015-03-12 15:47:06 UTC
I note that htcondor.so (the actual python package that is imported) has an RPATH set: $ chrpath --list /usr/lib64/python2.7/site-packages/htcondor.so /usr/lib64/python2.7/site-packages/htcondor.so: RUNPATH=$ORIGIN/../:/lib64:/usr/lib64:$ORIGIN/../condor so it will look in: /usr/lib64/python2.7/ /lib64 /usr/lib64 /usr/lib64/python2.7/condor for its link dependencies, So in the .spec file, libpyclassad2.7_%{srcver}.so could be installed to any of them. Created attachment 1001322 [details]
Install libpyclassad to the right location
Here's a suggestion for the fix for this problem.
Hi Matt Williams, im trying the above command to check libpyclassad but its not found, it shows me: [root@condorexec21 htcondorProject]# sudo ldd /usr/local/lib/python2.7/site-packages/htcondor.so | grep libpyclassad ldd: warning: you do not have execution permission for `/usr/local/lib/python2.7/site-packages/htcondor.so' /usr/local/lib/python2.7/site-packages/htcondor.so: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /usr/local/lib/python2.7/site-packages/htcondor.so) libpyclassad2.7_8_0_5.so => not found i checked /usr/lib/condor and did not contain libpyclassad2.7_8_0_5.so.! it contains other classad library version. should i add libpyclassad2.7_8_0_5.so to /usr/lib/condor? and where can i find it? thanks (I've updated Fedora so some version numbers here may have changed but nothing else has) libpyclassad2.7_8_3_1.so is currently installed to /usr/lib64/python2.7/site-packages/libpyclassad2.7_8_3_1.so by condor-python-8.3.1-1.fc21.x86_64 /usr/lib64/python2.7/site-packages/htcondor.so is looking for the file but the linker can't find it (that is what causes the "not found" error you posted above). With the current set up, libpyclassad2.7_8_3_1.so needs to be changed to be installed to one of the following: /usr/lib64/python2.7/ /lib64/ /usr/lib64/ /usr/lib64/python2.7/condor/ since these are the places that the linker is looking for it. I think that /usr/lib64/ ({_libdir} in RPM) probably makes the most sense. condor-8.3.8-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-bb2930f3a6 condor-8.3.8-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-dc8ffbb46b condor-8.3.8-1.fc21 has been submitted as an update to Fedora 21. https://bodhi.fedoraproject.org/updates/FEDORA-2015-a499c5d11f condor-8.3.8-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update condor' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-dc8ffbb46b condor-8.3.8-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update condor' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-bb2930f3a6 condor-8.3.8-1.fc21 has been pushed to the Fedora 21 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update condor' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-a499c5d11f condor-8.3.8-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. condor-8.5.0-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-296761c893 condor-8.5.0-1.fc21 has been submitted as an update to Fedora 21. https://bodhi.fedoraproject.org/updates/FEDORA-2015-7b408f7011 condor-8.5.0-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update condor' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-296761c893 condor-8.5.0-1.fc21 has been pushed to the Fedora 21 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update condor' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-7b408f7011 condor-8.5.0-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. condor-8.5.0-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. |