Container image upload can be unreliable -- retry needed?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Invalid
|
Medium
|
Unassigned |
Bug Description
I'm trying to locally reproduce a containerized environment on my virthost and my deployment stopped with:
TASK [overcloud-
in the logs I see:
2017-06-23 14:11:44 | + openstack overcloud container image upload --verbose --config-file /usr/share/
2017-06-23 14:11:45 | START with options: [u'overcloud', u'container', u'image', u'upload', u'--verbose', u'--config-file', u'/usr/
2017-06-23 14:11:45 | command: overcloud container image upload -> tripleoclient.
2017-06-23 14:11:45 | Using config files: [u'/usr/
2017-06-23 14:11:45 | imagename: tripleoupstream
2017-06-23 14:12:59 | Completed upload for docker image tripleoupstream
[..]
2017-06-23 14:15:04 | imagename: tripleoupstream
2017-06-23 14:15:40 | ('Connection broken: IncompleteRead(0 bytes read)', IncompleteRead(0 bytes read))
2017-06-23 14:15:40 | END return value: 1
Since then I restarted the script several time and it gets further and further, but it still did not get to the end of it in ~8 runs.
Either we need a retry in the quickstart preparation script, or rather the "openstack overcloud container image upload" command should have a retry, because this will be a problem for reproducers outside of tripleo upstream ci where the network connection might not be perfect.
Changed in tripleo: | |
status: | New → Triaged |
Fix proposed to branch: master /review. openstack. org/477521
Review: https:/