*pkgs* job is not retriggered on rechecks for python-fuelclient

[Roman Prykhodchenko]

Steps to reproduce:

1. Publish a patch for python-fuelclient that causes master.python-fuelclient.pkgs.ubuntu.review_fuel_client to fail
2. Wait for a -1 from Fuel-CI
3. Post a comment containing only "recheck" word

Expected: both verify-python-fuelclient and master.python-fuelclient.pkgs.ubuntu.review_fuel_client to fail get re-triggered.
Result: only verify-python-fuelclient gets retriggered.

This behavior was noticed on multiple patches for python-fuelclient. You can explore this one https://review.openstack.org/#/c/272975/.

Screenshot is attached.

[Sergey Kulanov (skulanov)]

set to critical, since this can introduce false positive results from ci

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/17916
Submitter: Aleksandra Fedorova <email address hidden>
Branch: master

Commit: e4af2008eee4310f1e02046d2115f55836abb551
Author: Aleksandra Fedorova <email address hidden>
Date: Fri Apr 15 11:44:15 2016

Add separate recheck for Fuel CI

Gerrit Trigger plugin calculates result per event. So if we run only
partial recheck for unit-tests, deployment test results are ignored
and patch gets Verified+1 even if it fails deployment.

Thus we can only recheck all tests at once.

We setup a separate keyword for Fuel CI, so that we do not restart
heavy deployment tests when there are failures in lightweight upstream
gate.

This patch:

* adds recheck Fuel CI jobs including deployment tests by comment:

    fuel: recheck

* adds rechecks for previously skipped fuel-library unit tests.

Closes-Bug: #1545253

Change-Id: I3a65de39e26ace451ce1798d5087b7db9bf24124