Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate why we don't pass task deployment properties when restarting the job execution #2807

Closed
ilayaperumalg opened this issue Jan 30, 2019 · 2 comments
Assignees
Labels
area/task-orchestration Belongs to task orchestration type/bug Is a bug report

Comments

@ilayaperumalg
Copy link
Contributor

ilayaperumalg commented Jan 30, 2019

The related discussion is here

Depends on #2733

@sabbyanandan
Copy link
Contributor

A community report on the same problem posted here.

@sabbyanandan sabbyanandan added the type/bug Is a bug report label Feb 7, 2019
@sabbyanandan sabbyanandan modified the milestones: 2.0.0.RC1, 2.1.0.M1 Feb 15, 2019
@sabbyanandan sabbyanandan removed the ready label Mar 8, 2019
@sabbyanandan sabbyanandan modified the milestones: 2.1.0.M1, 2.2.0.M1 Mar 22, 2019
@sabbyanandan sabbyanandan added the area/task-orchestration Belongs to task orchestration label Aug 5, 2019
@sabbyanandan sabbyanandan modified the milestones: 2.3.0.M1, Iteration 154 -> SCDF 2.3.0.RC1 Sep 11, 2019
@sabbyanandan
Copy link
Contributor

This will be addressed in #3121 in the context of #3407.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/task-orchestration Belongs to task orchestration type/bug Is a bug report
Projects
None yet
Development

No branches or pull requests

3 participants