Description of problem: The SAP resource agents included in RHEL 5.2 and RHEL 5.3 are out of date. The new ones need to be included for the best support of SAP's products on RHEL5. Updated agents were added as part of bug #239597 and are as follows: https://bugzilla.redhat.com/attachment.cgi?id=324950 https://bugzilla.redhat.com/attachment.cgi?id=324953 https://bugzilla.redhat.com/attachment.cgi?id=324954 These were provided by engineers at Atix and have been committed to the master branch of the cluster project, but have not been ported to RHEL5 or 5.3.
I would like to see this as an early update to RHEL 5.3 if possible, as it affects customer installations.
Mark, Licensing information in the updated agents does not specify what version of the GPL license is in force. The rest of the linux-cluster project is GPL v2+. Please advise if this license versioning is okay. -- Lon
Lon, as I'm not the author of the SAPDatabase and SAPInstance agents, I cannot change the license. We need to consult Alex Krauth for a license change there. For the follow_service script I agree to change the license to GPL v2+. -Mark
Updated.
Thanks :)
Hi Alexander, The recent updates to the SAPInstance / SAPDatabase resource agents are licensed with the GPL, but it doesn't specify which version. Our cluster stack uses the "GPL version 2 or later", since GPLv1 is not necessarily compatible with other licenses. Would it be possible for you to grant a license on those agents under "GPL, version 2 or (at your option) any later version", so we can exclude GPLv1? I can't simply change a license without authorization from the original author. -- Lon
Hi Lon, in some configurations, parts of the SAP binaries are hosted on a nfs fileserver. In this case, all SAP cluster resources need to define a netfs resource to be able to control the nfs mount. The problem with the current netfs agent is, that it unmounts the nfs filesystem with every stop and relocation operation. This causes all other resources running on the same server to fail, because the nfs mount is not available any more. To solve the problem, I added a no_umount parameter to the netfs agent, preventing the umount operation. Could you please take a look at the proposed changes ? Thanks a lot, Mark
Created attachment 328459 [details] patch with no_umount option
I'm ok with this change.
The following have been pushed to the RHEL5 branch. Mark's no_unmount patch: http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=705b1fc5472c69e09738149f4d95c9875971d76c Mark+Marc's follow-service patch: http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=f397e2e210651446205c319c6b60a051f55fa415 Updated resource agents: http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=9ef9ccf98218dcadc6f604a3ed8ca7aad67bc11b
An additional patch proposed during the testing phase of #479708 has been pushed to the RHEL5 branch: http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=1fe224ebf9a023a2a781c7d33661128bc2e5582a
Mark Hlawatschek, could you test this and report back?
~~ Attention - RHEL 5.4 Beta Released! ~~ RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner! If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity. Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value. Questions can be posted to this bug or your customer or partner representative.
~~ Attention Partners - RHEL 5.4 Snapshot 1 Released! ~~ RHEL 5.4 Snapshot 1 has been released on partners.redhat.com. If you have already reported your test results, you can safely ignore this request. Otherwise, please notice that there should be a fix available now that addresses this particular request. Please test and report back your results here, at your earliest convenience. The RHEL 5.4 exception freeze is quickly approaching. If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity. Do not flip the bug status to VERIFIED. Instead, please set your Partner ID in the Verified field above if you have successfully verified the resolution of this issue. Further questions can be directed to your Red Hat Partner Manager or other appropriate customer representative.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-1339.html