Bug 693567 - unable to delete replica if replica is not available.
Summary: unable to delete replica if replica is not available.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-04 23:29 UTC by Michael Gregg
Modified: 2015-01-04 23:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-05 13:39:22 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Michael Gregg 2011-04-04 23:29:47 UTC 
Description of problem:
If a ipa replica becomes unavailable, or otherwise offline, I am unable to delete that replica from the domain

Version-Release number of selected component (if applicable):
ipa-server-2.0.0-18.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. install a ipa server
2. set up a replica server 
3. ensure that the domain contains the two replicas with ipa-replica-manage --list
4. power off the replica.
5. ipa-replica manage del <replica>
  
Actual results:
[root@ipaqa64vma ~]# ipa-replica-manage del ipaqa64vmb.testrelm
Unable to delete replica ipaqa64vmb.testrelm: {'desc': "Can't contact LDAP server"}

Expected results:
Messages like, "Unable to contact replica, remove anyway? yes/(no)
Comment 2 RHEL Program Management 2011-04-04 23:43:30 UTC 
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 3 Rob Crittenden 2011-04-05 13:39:22 UTC 
If the remote replica is not available use the --force flag.
Note You need to log in before you can comment on or make changes to this bug.