Description of problem: Found this issue during tps-rpm test. Currently auth plugin config file could be named to any, just make sure the config file has ".conf" suffix should be ok. # rpm -qp --scripts rubygem-openshift-origin-auth-remote-user-1.8.2-1.el6op.noarch.rpm postinstall scriptlet (using /bin/sh): if [ $1 -ne 1 ] # this is an update; fix the previously configured realm. then sed -i -e 's/AuthName.*/AuthName "OpenShift Broker API"/' /var/www/openshift/broker/httpd/conf.d/openshift-origin-auth-remote-user.conf fi Now issue comes, if user has auth config file named "xxx.conf", then update rubygem-openshift-origin-auth-remote-user package using "rpm -Uhv", it will throw the following error message: # rpm -Uhv rubygem-openshift-origin-auth-remote-user-1.8.2-1.el6op.noarch.rpm sed: can't read /var/www/openshift/broker/httpd/conf.d/openshift-origin-auth-remote-user.conf: No such file or directory warning: %post(rubygem-openshift-origin-auth-remote-user-1.8.2-1.el6op.noarch) scriptlet failed, exit status 2 Version-Release number of selected component (if applicable): rubygem-openshift-origin-auth-remote-user-1.8.2-1.el6op.noarch.rpm How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
We need to backport https://github.com/openshift/origin-server/commit/d2e35f26571065963f2294d2b5a0881059ce9e0a
Pull request: https://github.com/openshift/enterprise-server/pull/135 This is direct cherry-picking of the commit mentioned in comment 2, but in light of bug 999182, should we try to be a little more clever in case the .conf file has a different name?
I'm OK will keeping the filename guessing logic in oo-diagnostics and keeping the %post logic the same as upstream.
Merged: https://github.com/openshift/enterprise-server/commit/d91e027b90f23c8c6a2e0c27d4a4dc433811fe42
Verified this bug with rubygem-openshift-origin-auth-remote-user-1.8.3-1.el6op.noarch, and PASS. # rpm -Uhv rubygem-openshift-origin-auth-remote-user-1.8.3-1.el6op.noarch.rpm Preparing... ########################################### [100%] 1:rubygem-openshift-origi########################################### [100%]
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1275.html