CI: scenario002 job fails when not finding centos-binary-barbican-keystone-listener container
Bug #1736411 reported by
Sagi (Sergey) Shnaidman
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Sagi (Sergey) Shnaidman |
Bug Description
tripleo-
2017-12-05 07:50:07 | docker pull failed: Tag ac82ea9271a4ae3
We build this container:
https:/
but don't promote it, because it's not in list:
https:/
Changed in tripleo: | |
milestone: | none → queens-3 |
Changed in tripleo: | |
assignee: | nobody → Sagi (Sergey) Shnaidman (sshnaidm) |
Changed in tripleo: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
Promoted manually, should be ok now: /hub.docker. com/r/tripleoma ster/centos- binary- barbican- keystone- listener/ tags/
https:/