EMS docker image not propagated to Quay.io, after change has been committed
Bug #2065276 reported by
ipatini
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| NebulOuS |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
Related change:
https:/
After the changed has been merged, the propagation pipeline didn't start (at least till the time i write this report), and the docker image has not been pushed to quai.io
As a result, EMS server at nebulous-cd has been restarted but re-used the older docker image (which is still tagged 'latest')
Revision history for this message
| ipatini (ipatini) wrote | #1 |
| Changed in nebulous: | |
| status: | New → Won't Fix |
| assignee: | Jan Marchel (janmarchel7bulls) → nobody |
Revision history for this message
| Radosław Piliszek (yoctozepto) wrote | #2 |
To post a comment you must log in.
Seems a subsequent change forced latest docker image to be propagated to quay.io