unpaired peer couchdb is not updated not to pull from us

Bug #451591 reported by Chad Miller
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
desktopcouch
Fix Released
Medium
Unassigned

Bug Description

If one pairs with a peer and subsequently uses the pairing tool to un-pair with the peer, we change the local status of the pairing, but the peer may not be online and available to tell also to unpair.

We should queue that operation for the next time we see the peer, and then go alter its management database, but we do not yet do that successfully. Instead, we will see this in the log file:

2009-10-14 15:55:32,425 - failed to unpair from other end.
Traceback (most recent call last):
  File "/home/cmiller/work/desktopcouch/trunk/desktopcouch/replication.py", line 102, in do_all_replication
    raise last_exception
TypeError: expunge_pairing() takes at most 2 arguments (3 given)

Revision history for this message
Chad Miller (cmiller) wrote :

Workaround: On the far machine, use the futon interface at
file:///home/$USERNAME/.local/share/desktop-couch/couchdb.html
to remove the pairing id in the management database.

Changed in desktopcouch:
importance: Undecided → Medium
Chad Miller (cmiller)
Changed in desktopcouch:
assignee: Chad Miller (cmiller) → nobody
JACQUELINE (ijdisabest)
Changed in desktopcouch:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.