Open Stack

On 05/24/2018 08:45 PM, Ian Wienand wrote:
> On 05/24/2018 05:40 PM, Ian Wienand wrote:
>> In an effort to resolve this, the afs01 & 02 servers were restarted to
>> clear all old transactions, and for the affected mirrors I essentially
>> removed their read-only copies and re-added them with:
> 
> It seems this theory of removing the volumes and re-adding them is not
> sufficient to get things working; "vos release" is still failing.  I
> have sent a message to the openafs-devel list [1] with details and
> logs.

Thanks to the help of Jeffrey Altman [1], we have managed to get
mirror.pypi starting to resync again.  This is running in the root
screen on mirror-update.o.o (sorry, I forgot the "-v" on the command).

For reference, you can look at the transaction and see it receiving
data, e.g.

 root at afs02:/var/log/openafs# vos status -verbose -server localhost -localauth 
 Total transactions: 1
 --------------------------------------
 transaction: 62  created: Thu May 24 12:58:23 2018
 lastActiveTime: Thu May 24 12:58:23 2018
 volumeStatus: 
 volume: 536870932  partition: /vicepa  procedure: Restore
 packetRead: 2044135  lastReceiveTime: Thu May 24 13:33:17 2018
 packetSend: 1  lastSendTime: Thu May 24 13:33:17 2018
 --------------------------------------

Assuming this goes OK over the next few hours, that leaves
mirror.ubuntu and mirror.ubuntu-ports as the last two out-of-sync
mirrors.  As we do not want to run large releases in parallel, we can
tackle this when pypi is back in sync.

Thanks,

-i

[1] http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2018-05-24.log.html#t2018-05-24T12:57:39