fuel graph utility does not filter tasks by "--start" and "--end" arguments

[Stepan Rogov]

fuel graph utility does not filter tasks by "--start" and "--end" arguments
Checked on the MOS 7.0 and 8.0 on deployed environments

When I run:
fuel graph --env 1 --download --start post_deployment_start --end post_deployment_end --remove skipped

I've get all tasks in output
But I expect to get a filtered output which should be contain only tasks from post_deployment stage

[Bulat Gaifullin (bulat.gaifullin)]

The Task based deployment engine does not operate with graph and there is no way to get tasks from start and end.
Also, functionality launch selected tasks should be deprecated by feature 'custom_graph'. the custom graph allows user to launch any combination of tasks.

[Denis Meltsaykin (dmeltsaykin)]

Why does this issue have High importance? What is the real impact on running OpenStack environments? Lowering this to medium for "updates" until someone explains how this affects workloads.

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[Alexey Shtokolov (ashtokolov)]

Stepan, could you please explain what do you mean in case of task-based deployment?

[Alexey Shtokolov (ashtokolov)]

Stepan, these handlers do not work with task-based deployment. Because there is no way to determine actual order of tasks when the task execution depends on tasks on other nodes.

[Denis Meltsaykin (dmeltsaykin)]

Setting as Invalid per comment #6.