Bug 233129 - AEP: failover info is not cached properly?
AEP: failover info is not cached properly?
Product: Red Hat Certificate System
Classification: Red Hat
Component: Auto-Enrollment (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: Brian Stevens
Chandrasekar Kannan
Depends On:
  Show dependency treegraph
Reported: 2007-03-20 12:00 EDT by Chandrasekar Kannan
Modified: 2017-04-10 10 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-08-28 20:08:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chandrasekar Kannan 2007-03-20 12:00:27 EDT
AEP - proxy failover.

I have two CA's placed in the AEP configuration.

ca #1 : ivanova.dsqa.sjc2.redhat.com: 15443
ca #2 : switch.dsdev.sjc.redhat.com:15443

I shutdown CA#1. 

the 1st certificate request failed over to ca#2 as expected.
the 2nd certificate request also failed over to ca#2. 

Steve, per your design, this shouldn't be happening , right ?.

if ca#1 is down, this info is cached for 5 minutes and subsequent
certificate requests should go directly to ca#2 ?.
Comment 1 Steve Parkinson 2007-03-29 13:54:18 EDT
Sorry, the default retry interval is 30 seconds. You can change this value in
the registry. I documented it in appendix 2 of the documentation.


Comment 2 Steve Parkinson 2007-04-02 12:30:25 EDT
Is this a dupe of : bug 233044 ?
Comment 3 Chandrasekar Kannan 2007-04-21 13:44:13 EDT
Verified with CS 7.3 build 04/20

used windows2003sp1 - child domain to do autoenrollment.
setup failover connections to the following CAs.
  1. CS 71 CA
  2. CS 72 CA

They are both subordinates of the same rootCA.

1. stopped CS71CA. AEP failed over to the 72CA.
2. stopped CS72CA. AEP failover over to the 71CA.

failover caching works ok.
Comment 4 Red Hat Bugzilla 2007-11-04 23:21:32 EST
User sparkins@redhat.com's account has been closed
Comment 5 Chandrasekar Kannan 2008-08-25 18:54:08 EDT
Bug already CLOSED/VERIFIED. setting screened+ flag

Note You need to log in before you can comment on or make changes to this bug.