Red Hat Bugzilla – Bug 1032901
Packages installed via Jenkins builds fail to take effect for Perl apps
Last modified: 2015-05-14 20:34:57 EDT
Description of problem:
Given a Perl-5.10 app with a Jenkins-client added, when trying to install a package to this app, the package fails to take effect with Jenkins build even though no error is reported during the installation. Moreover, a page referencing this package shows 500 error when accessing it. On the other hand, there is no such problem without Jenkins builds.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a Perl-5.10 app with a Jenkins-client added
rhc app create prl perl-5.10 --enable-jenkins
2. add a package to deplist.txt, for example,
echo "Plack" > deplist.txt
3. create a new page with the following code under $APP_REPO/perl/:
print "Succeed to install Plack!"
4. push the change and trigger a Jenkins build
5. access the $APP_DNS/test.pl
6. create another Perl-5.10 app WITHOUT adding a Jenkins-client
7. repeat step 2 ~ 5
In Step 5, the test.pl page returns "Internal Server Error", while the page returns the expected string without Jenkins build.
The Perl package should take effect after a Jenkins build.
The bug only happens when installing a non-system-supported package, and it goes away when trying to install a system-supported one, like YAML.
The problem seems to be that Jenkins install all dependencies to OPENSHIFT_DEPENDENCY_DIR but the PERL5LIB is not set to look into this directory...
Commit pushed to master at https://github.com/openshift/origin-server
Bug 1032901 - Removed perl5lib folder from GIT and added to dependency_dirs
Verified in devenv_4067.