As mentioned at those email - "reverify bug #" must work. " You may still use "reverify bug #" to re-enqueue if there is a bug report for a failure, and of course you are encouraged to file a bug report if there is not. Elastic-recheck is doing a great job of indicating which bugs might have caused a failure."
So, i guess we should investigate Gary's problem. Best regards, Denis Makogon. On Mon, Feb 17, 2014 at 2:53 PM, Sylvain Bauza <sylvain.ba...@gmail.com>wrote: > Hi Gary, > > That's normal, this command has been removed since Dec'13, see > http://lists.openstack.org/pipermail/openstack-dev/2013-December/021649.html > > -Sylvain > > > 2014-02-17 13:00 GMT+01:00 Gary Kotton <gkot...@vmware.com>: > >> Hi, >> It seems that the command 'reverify bug <number>' is not working. Anyone >> else experienced this lately. >> Thanks >> Gary >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
