Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1600559

Summary: FFU: Error inspecting image: docker://registry.access.redhat.com read tcp 10.9.65.105:60672->10.4.204.31:443: read: connection reset by peer"
Product: Red Hat OpenStack Reporter: Chris Janiszewski <cjanisze>
Component: openstack-tripleo-commonAssignee: Emilien Macchi <emacchi>
Status: CLOSED ERRATA QA Contact: Marius Cornea <mcornea>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: aschultz, augol, emacchi, jschluet, mburns, mcornea, morazi, slinaber
Target Milestone: z2Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-common-8.6.3-2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-29 16:37:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
undercloud-sos none

Description Chris Janiszewski 2018-07-12 13:45:17 UTC
Created attachment 1458420 [details]
undercloud-sos

Description of problem:
I am hitting this inconsistent problem when preparing overcloud images:

openstack overcloud container image prepare \
  --namespace=registry.access.redhat.com/rhosp13 \
  --push-destination=172.16.0.11:8787 \
  --prefix=openstack- \
  --tag-from-label {version}-{release} \
  --output-env-file=/home/stack/templates/overcloud_images.yaml \
  --output-images-file /home/stack/local_registry_images.yaml

Error inspecting image: docker://registry.access.redhat.com/rhosp13/openstack-aodh-listener:latest
time="2018-07-12T09:24:28-04:00" level=fatal msg="Get https://registry.access.redhat.com/v2/rhosp13/openstack-aodh-listener/manifests/latest: read tcp 10.9.65.105:60672->10.4.204.31:443: read: connection reset by peer" 

The inconsistency is that it might work fine on a first try, but it might as well error out on first 2 tries and work on the 3rd try.
It almost seems like there is multiple docker repository with not all of them being operational and load balancing puts me on random ones and not re-tries at failure.

I am repeating this process over and over again and it's all scripted on my end, so there is little to no room for user error (unless my script is wrong).

Also the service that the error complains about is usually different. In this case it's openstack-aodh-listener, but I have seen others as well


Version-Release number of selected component (if applicable):
OSP13

How reproducible:
inconsistent

Steps to Reproduce:
1.Run the upgrade process from OSP10 to OSP13
2.Invoke openstack overcloud container image prepare as part of the process


Actual results:
Error inspecting image: docker://registry.access.redhat.com/rhosp13/openstack....read: connection reset by peer" 

Expected results:
successful completion .. maybe even after multiple re-tries if necessary 

Additional info:
attaching sos from undercloud

Comment 2 Emilien Macchi 2018-07-12 15:57:32 UTC
I think what we want here is a backport of https://review.openstack.org/#/c/579734/. I'll look at this one today.

Comment 3 Chris Janiszewski 2018-07-12 16:36:31 UTC
FYI - I just hit it again on another env with different service:

Error inspecting image: docker://registry.access.redhat.com/rhosp13/openstack-neutron-metadata-agent:latest
time="2018-07-12T12:39:36-04:00" level=fatal msg="Get https://registry.access.redhat.com/v2/rhosp13/openstack-neutron-metadata-agent/manifests/latest: read tcp 10.9.65.117:51226->10.4.204.31:443: read: connection reset by peer"

Comment 13 Joanne O'Flynn 2018-08-15 07:51:55 UTC
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible.

If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-".


To add draft documentation text:

* Select the documentation type from the "Doc Type" drop down field.

* A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.

Comment 15 errata-xmlrpc 2018-08-29 16:37:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2574