Red Hat Bugzilla – Bug 707127
Last modified: 2011-12-06 07:03:00 EST
Initial evaluation shows that we can rebase safely based on a new tarball
released from upstream.
1) move to standalone tarball
2) kill patch queue from distcvs
3) simplify build / spec file
4) update all pacemaker (TechPreview) agents
from distcvs RHEL6 branch in current release:
sed -i -e 's#\-b .*##g' resource-agents.spec
diff -Naurd resource-agents-3.0.12 resource-agents-3.9.1 | filterdiff -i
'*rgmanager*' -x '*Makefile*' | less
rgmanager/src/resources/SAPDatabase: resource-agents: Improve
LD_LIBRARY_PATH handling by SAP*
*.sl: moved back to rgmanager tree
missing *.sl scripts (upstream is in, needs backport to RHEL6)
rgmanager/src/resources/ocf-shellfuncs: resource-agents: Add resource
type to logging
tomcat-5.sh: rhbz#637802 (not in RHEL6)
config-utils.sh.in: rhbz#637802 (tomcat-5) and rhbz#667217
rhev-check.sh: RHEL6 specific patch, not upstream. (see rhbz#609497)
common: add license info to all agents (no code changes)
update: pacemaker agents, tech-preview
TODO: move rhev-check upstream and drop distcvs patch (Optional)
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
This update fixes a few bugs, and will make future updates easier.
Unit test results:
> rgmanager/src/resources/ocf-shellfuncs: resource-agents: Add resource
> type to logging
Jun 21 20:13:53 rgmanager [ip] Link for eth0: Detected
Jun 21 20:13:53 rgmanager [ip] Link detected on eth0
Jun 21 20:14:13 rgmanager [ip] Checking 192.168.0.128, Level 0
Jun 21 20:14:13 rgmanager [ip] 192.168.0.128 present on eth0
Jun 21 20:14:13 rgmanager [ip] Link for eth0: Detected
Jun 21 20:14:13 rgmanager [ip] Link detected on eth0
Jun 21 20:14:23 rgmanager [ip] Checking 192.168.0.128, Level 10
now reports the agent name in 
> rhev-check.sh: RHEL6 specific patch, not upstream.
rpm -q -p resource-agents-3.9.1-1.el6.x86_64.rpm -l |grep rhev
It´s now included upstream and not in a separate patch.
Items that need unit test results:
> oracledb.sh.in: rhbz#633992
> svclib_nfslock: rhbz#595455
I can't test 663992, so I reviewed the patch:
* In most cases, we now call 'stop_db immediate'. During forceful shutdown, we switch to 'stop_db abort' if 'stop_db immediate fails'
I created an NFS failover service to test the svclib_nfslock changes.
* With no clients, the expectation was that there is no creation of /tmp/statd-*; this behavior worked correctly, although I did have to tweak /etc/sysconfig/nfs to disable NFS version 4 support in order to use it with the nfsexport/nfsclient mechanisms that use the nfslock="1" attribute.
*** Bug 698217 has been marked as a duplicate of this bug. ***
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.