Bug 304931

Summary: Rich Sybase resource agent configuration support
Product: Red Hat Enterprise Linux 5 Reporter: Rob Kenna <rkenna>
Component: congaAssignee: Jim Parsons <jparsons>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: high    
Version: 5.0CC: cluster-maint, jphui, kanderso, lhh, poelstra, rmccabe
Target Milestone: ---Keywords: Documentation, FutureFeature, OtherQA
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2008-0407 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-21 15:47:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 435795    
Bug Blocks:    

Description Rob Kenna 2007-09-25 12:52:07 UTC
In conjunction with Sybase, build and certify a standard Sybase failover agent.
 This work is currently being carried out as joint development

Comment 1 Kiersten (Kerri) Anderson 2007-11-05 23:22:12 UTC
Removing the 5.2 flag, no work identified on our side as of yet.

Comment 2 Rob Kenna 2007-11-06 14:48:54 UTC
Re-asserting for 5.2 since Sybase has just provided this, including detailed doc.

Comment 3 Rob Kenna 2007-11-06 14:54:23 UTC
To be clear, Sybase has completed this work.  We simply need to integrate into
the release ad add Conga configuration support

Comment 4 Rob Kenna 2007-11-07 18:26:18 UTC
Reassigning to the Conga team as the primary work is in UI integration.  We
still need to place the module in the distribution.

Comment 5 Rob Kenna 2007-11-07 18:27:30 UTC
Also needed is the integration of the doc into or alongside ours.

Comment 7 Rob Kenna 2008-03-04 15:13:57 UTC
bug 435795 contains the specific resource agent request along with the
attachments of the doc and resource agent.

Comment 14 John Poelstra 2008-04-02 21:38:16 UTC
Greetings Red Hat Partner,

A fix for this issue should be included in the latest packages contained in
RHEL5.2-Snapshot3--available now on partners.redhat.com.  

Please test and confirm that your issue is fixed.

After you (Red Hat Partner) have verified that this issue has been addressed,
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)

If this issue is not fixed, please add a comment describing the most recent
symptoms of the problem you are having and change the status of the bug to ASSIGNED.

If you are receiving this message in Issue Tracker, please reply with a message
to Issue Tracker about your results and I will update bugzilla for you.  If you
need assistance accessing ftp://partners.redhat.com, please contact your Partner
Manager.

Thank you


Comment 15 John Poelstra 2008-04-09 22:44:14 UTC
Greetings Red Hat Partner,

A fix for this issue should be included in the latest packages contained in
RHEL5.2-Snapshot4--available now on partners.redhat.com.  

Please test and confirm that your issue is fixed.

After you (Red Hat Partner) have verified that this issue has been addressed,
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)

If this issue is not fixed, please add a comment describing the most recent
symptoms of the problem you are having and change the status of the bug to ASSIGNED.

If you are receiving this message in Issue Tracker, please reply with a message
to Issue Tracker about your results and I will update bugzilla for you.  If you
need assistance accessing ftp://partners.redhat.com, please contact your Partner
Manager.

Thank you


Comment 16 John Poelstra 2008-04-23 17:39:32 UTC
Greetings Red Hat Partner,

A fix for this issue should be included in the latest packages contained in
RHEL5.2-Snapshot6--available now on partners.redhat.com.  

We are nearing GA for 5.2 so please test and confirm that your issue is fixed ASAP.

After you (Red Hat Partner) have verified that this issue has been addressed,
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)

If this issue is not fixed, please add a comment describing the most recent
symptoms of the problem you are having and change the status of the bug to ASSIGNED.

If you are receiving this message in Issue Tracker, please reply with a message
to Issue Tracker about your results and I will update bugzilla for you.  If you
need assistance accessing ftp://partners.redhat.com, please contact your Partner
Manager.

Thank you


Comment 17 John Poelstra 2008-05-01 16:49:46 UTC
Greetings Red Hat Partner,

A fix for this issue should be included in the latest packages contained in
RHEL5.2-Snapshot7--available now on partners.redhat.com.  

We are nearing GA for 5.2--this is the last opportunity to test and confirm that
your issue is fixed.

After you (Red Hat Partner) have verified that this issue has been addressed,
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)

If this issue is not fixed, please add a comment describing the most recent
symptoms of the problem you are having and change the status of the bug to ASSIGNED.

If you are receiving this message in Issue Tracker, please reply with a message
to Issue Tracker about your results and I will update bugzilla for you.  If you
need assistance accessing ftp://partners.redhat.com, please contact your Partner
Manager.

Thank you

Comment 18 Brian Brock 2008-05-15 02:34:41 UTC
Functionality and configuration user interface is present, without obvious
defects.  Changing state to verified, in -7.el5

Please note that this bug doesn't cover any specific in-depth testing of Sybase
support.

Comment 20 errata-xmlrpc 2008-05-21 15:47:21 UTC
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/RHBA-2008-0407.html