Different DLRN hashes in same job for current-tripleo
Bug #1769901 reported by
Sagi (Sergey) Shnaidman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
Medium
|
Sagi (Sergey) Shnaidman | ||
Bug Description
In job http://
were different hashes for current-tripleo for containers and repositories. Seems like race condition when running job during promotion process.
Revision history for this message
| Matt Young (halcyondude) wrote | #1 |
Revision history for this message
| Matt Young (halcyondude) wrote | #2 |
| Changed in tripleo: | |
| importance: | High → Medium |
| Changed in tripleo: | |
| milestone: | rocky-2 → rocky-3 |
| Changed in tripleo: | |
| milestone: | rocky-3 → rocky-rc1 |
| Changed in tripleo: | |
| milestone: | rocky-rc1 → stein-1 |
| Changed in tripleo: | |
| milestone: | stein-1 → stein-2 |
| Changed in tripleo: | |
| milestone: | stein-2 → stein-3 |
| Changed in tripleo: | |
| milestone: | stein-3 → train-1 |
| Changed in tripleo: | |
| milestone: | train-1 → train-2 |
| Changed in tripleo: | |
| milestone: | train-2 → train-3 |
| Changed in tripleo: | |
| milestone: | train-3 → ussuri-1 |
| Changed in tripleo: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
As a data point, we were generally plagued with this issue in RDO 2 (in 2016) until we started explicitly passing the hash as an input at the top level, and stopped (completely) accessing any hashes or repo's via symbolic link.