This happened because of the changes we did with ssh-keys used for replication. I'd forgotten that this had been done, and was expecting pushes to happen automatically.
Earlier, a single users key was used (key of one of the admins of the gluster organization, Avati initially) to push changes from gerrit to github. This enabled all repositories in gerrit to be automatically be pushed into to its replica in github (<project-name> in gerrit would be automatically pushed to github/<project-name>). This key got changed/deleted which caused replication to fail a while back. To avoid tying pushes to a single user like this, a separate key was setup for each github repo, and gerrit was setup to use the respective keys to push to each repo. This requires manual replication configuration. This change was implemented only for the glusterfs and glusterfs-specs repos. All other repos require manual configuration. We'll try to comeup with a better way to do this replication. If we can't, we'll need to manually set up the keys and encryption for each repo. ~kaushal On Wed, Mar 9, 2016 at 12:22 PM, Prashanth Pai <[email protected]> wrote: > Hi, > > The github mirror[1] sync is broken for libgfapi-python and gluster-swift > repos[2]. > Can someone please take a look ? > > Thanks. > > [1]: Github mirrors: > https://github.com/gluster/libgfapi-python > https://github.com/gluster/gluster-swift > > [2]: Gerrit repos: > git://review.gluster.org/libgfapi-python > git://review.gluster.org/gluster-swift > > Regards, > -Prashanth Pai > _______________________________________________ > Gluster-infra mailing list > [email protected] > http://www.gluster.org/mailman/listinfo/gluster-infra _______________________________________________ Gluster-infra mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-infra
