Support for scenario serialization/deserialization
Extract control flow of upgrades to special file
Don't continue with scenarios when last is not finished
Move sync-plans checks to pre/post migrations
Introduce run_strategy for scenarios
Health-check scenarios are better to run all steps regardless of errors(:fail_slow strategy), while the migration scenarios should fail as soonas first failure happens (:fail_fast strategy).
By default, the scenarios are treated as `:fail_fast`.
Add --whitelist option
Allows to mark some steps to be ignored in the results: allows tocontinue even when some checks are failing.
Full upgrade scenario
This commit intoroduces more structured upgrade scenario consisting ofthis scenarios:
Retain original objects while Tsorting. TSort create label graph and then convert to object graph
Define order using ruby TSort
1. Introduce 2 metadata: 'before' and 'after'2. Current order is:Checks::SyncPlans::WithEnabledStatusChecks::DiskSpeedMinimalChecks::SystemRegistrationChecks::ForemanTasks::NotPausedChecks::ForemanTasks::NotRunningChecks::ForemanTasks::Invalid::CheckOld...
Fixes #59 - missing error for hammer-config file
View revisions
Also available in: Atom