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

No indication of failure when subsequent stages are run after material config is changed post first stage run #6409

Closed
msaurabh1978 opened this issue Jun 11, 2019 · 5 comments

Comments

@msaurabh1978
Copy link
Contributor

commented Jun 11, 2019

Issue Type
  • Bug Report
Summary

This bug is reproducible every time when a pipeline has more than one manual stage and more than one materials configured. After the first stage, if we change the pipeline material configuration, let's say by removing one of the configured material, then the subsequent stage run fails. But there is no information regarding the failure, neither in the server logs nor in the job console logs.

Steps to Reproduce
  • Create a pipeline with more than one manual stage and more than one materials
  • Run the first stage successfully
  • Modify the pipeline material configuration, let's say by removing one of the configured material
  • Run the next stage.
  • You will see that there is no information regarding the failure (neither in server logs nor in console logs)
Expected Results

Information regarding why the stage run failed should be logged in console logs so that user can easily understand the reason for failure.

Actual Results

Currently, when a stage fails after following the above steps to reproduce, there is absolutely no information available anywhere.

@arvindsv

This comment has been minimized.

Copy link
Member

commented Jun 11, 2019

@msaurabh1978 Is this the same as #6376 ?

@msaurabh1978

This comment has been minimized.

Copy link
Contributor Author

commented Jun 13, 2019

#6376

Not sure @arvindsv, doesn't look like but will check and confirm back.

@arvindsv

This comment has been minimized.

Copy link
Member

commented Jun 19, 2019

@msaurabh1978 Did you find anything?

@msaurabh1978

This comment has been minimized.

Copy link
Contributor Author

commented Jun 20, 2019

@msaurabh1978 Did you find anything?

Yeah. Found the root cause and fixed it (PR is #6389). Both of these issues, though symptom wise, unrelated, happened to originate from the same cause. I will provide all the details on issue #6376

@maheshp maheshp removed this from In progress in 19.6.0 Jul 17, 2019

@maheshp maheshp added this to In progress in 19.7.0 Jul 17, 2019

@maheshp maheshp removed this from In progress in 19.7.0 Jul 25, 2019

@maheshp maheshp added this to In progress in 19.8.0 Jul 25, 2019

@rajiesh rajiesh moved this from In progress to Done in 19.8.0 Sep 6, 2019

@rajiesh

This comment has been minimized.

Copy link
Contributor

commented Sep 6, 2019

Verified on 19.8.0 (9912-33898b3adaf72cedea1604882d3554fd586571a8)

@rajiesh rajiesh closed this Sep 6, 2019

@rajiesh rajiesh moved this from Done to QA Done in 19.8.0 Sep 6, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
4 participants
You can’t perform that action at this time.