Comment 3 for bug 1826912

As a matter of fact, if we try to execute system-apply after failure, it is going to be stucked on 26% showing the following message from sysinv.log

 processing chart: osh-openstack-garbd, overall completion: 26.0%
2019-04-29 12:13:48.466 7345 INFO sysinv.api.controllers.v1.host [-] controller-0 ihost_patch_start_2019-04-29-12-13-48 patch
2019-04-29 12:13:48.467 7345 INFO sysinv.api.controllers.v1.host [-] controller-0 ihost_patch_end. No changes from mtce/1.0.
2019-04-29 12:13:49.099 7344 INFO sysinv.api.controllers.v1.host [-] compute-1 ihost_patch_start_2019-04-29-12-13-49 patch
2019-04-29 12:13:49.102 7344 INFO sysinv.api.controllers.v1.host [-] compute-1 ihost_patch_end. No changes from mtce/1.0.
2019-04-29 12:13:49.201 7344 INFO sysinv.api.controllers.v1.host [-] compute-0 ihost_patch_start_2019-04-29-12-13-49 patch
2019-04-29 12:13:49.202 7344 INFO sysinv.api.controllers.v1.host [-] compute-0 ihost_patch_end. No changes from mtce/1.0.
2019-04-29 12:13:58.117 7344 INFO sysinv.api.controllers.v1.host [-] controller-1 ihost_patch_start_2019-04-29-12-13-58 patch
2019-04-29 12:13:58.118 7344 INFO sysinv.api.controllers.v1.host [-] controller-1 ihost_patch_end. No changes from mtce/1.0.