On Mon, Mar 16, 2020 at 7:25 PM [email protected] <[email protected]> wrote: > > Hi numans, > The issue I discribed in this change is repeated. When I restart the > ovn-northd of the first server(which has transfered its leadership), it will > be stucked. > The problem of robot replys seems reasonable. Do I need to take > checksum or something for utilities/ovn-ctl ?
Hi Yun, I think the robot is trying to apply this patch to OVS repo instead of OVN, since you don't have "ovn" tag i.e "PATCH ovn". So no need to worry about this. I think your patch makes sense. But I'd like if Han can take a look at this patch. Acked-by: Numan Siddique <[email protected]> Numan > > > Thanks, > Yun > -------------- > [email protected] > >Bleep bloop. Greetings Tao YunXiang, I am a robot and I have tried out your > >patch. > >Thanks for your contribution. > > > >I encountered some error that I wasn't expecting. See the details below. > > > > > >git-am: > >error: sha1 information is lacking or useless (utilities/ovn-ctl). > >error: could not build fake ancestor > >hint: Use 'git am --show-current-patch' to see the failed patch > >Patch failed at 0001 ovn-ctl: Add "--no-leader-only" while cluster db init > >When you have resolved this problem, run "git am --continue". > >If you prefer to skip this patch, run "git am --skip" instead. > >To restore the original branch and stop patching, run "git am --abort". > > > > > >Please check this out. If you feel there has been an error, please email > >[email protected] > > > >Thanks, > >0-day Robot > _______________________________________________ > dev mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-dev _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
