Minor updates on Pike can fail with "socket is already closed"
Bug #1757487 reported by
Jiří Stránský
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Quite a confusing output from a failed update, probably due to Zaqar messaging issues:
u' "stdout: Trying to pull repository 192.168.
u' "2018-03-19.3: Pulling from 192.168.
u' "9a32f102e677: Already exists", ',
u' "b8aa42cec17Waiting for messages on queue 'f813b1b0-
socket is already closed.
a: Already exists", ',
u' "23a4bb7bf8d1: Already exists", ',
u' "3f0a54d105a8: Already exists", ',
u' "1f1ad46b4704: Already exists", ',
u' "f51d192f486a: Pulling fs layer", ',
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
Where is this output coming from?
The 'socket is already' closed sounds like a UI error message.