epam / epam/cloud-pipeline

The run failed with "NodeLost" status

Open
#285 1 comment 0 reactions 0 assignees View on GitHub
cloud/azure kind/bug sys/e2e
Dominant language
Java
Stars
163
Forks
65
Avg merge
11h 46m
Merged PRs (30d)
29

Description

**NOTE**: Such behavior doesn't appear constantly, "flaky" bug.

- Environment: AZURE
- Version: 0.15.0.944.582d8809f2
- Step to reproduce:

1. Create a shell template pipeline
2. Launch the created pipeline
4. Click on the just-launched run at "ACTIVE RUNS" tab on Runs page

**Exp**.: The run is running
**Act**.: The run failed with "NodeLost" status and run tasks were not executed

![image](https://user-images.githubusercontent.com/23356251/57775772-73fe0280-7726-11e9-83ad-e4084e6470b2.png)

As we can see from pipeline logs:

`AutoscaleManager - Failed to load pipeline run 1297.
[ERROR] 2019-05-15 00:21:33.258 [taskScheduler-3] AutoscaleManager - Pipeline with requested id: '1,297' was not found.
java.lang.IllegalArgumentException: Pipeline with requested id: '1,297' was not found.
at org.springframework.util.Assert.notNull(Assert.java:134) ~[spring-core-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at com.epam.pipeline.manager.pipeline.PipelineRunManager.loadPipelineRun(PipelineRunManager.java:380)`

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with PipelineRunManager.java at loadPipelineRun, then trace the AutoscaleManager path shown in the logs. Reproduce the shell template pipeline on Azure and follow the run from the ACTIVE RUNS tab. Done means the run does not become NodeLost because its pipeline run cannot be loaded, and the run tasks execute as expected.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, java, spring
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.