tripleo

  1. Bug #1815576
  2. Comment #15

Comment 15 for bug 1815576

Revision history for this message
Emilien Macchi (emilienm) wrote :

It also seems to happen with image-serve (without Docker Registry v2):

http://logs.openstack.org/61/637861/2/check/tripleo-ci-centos-7-scenario001-standalone/d8575f5/logs/undercloud/var/log/httpd/image_serve_access.log.txt.gz

192.168.24.1 - - [20/Feb/2019:00:36:48 +0000] "HEAD /v2/tripleomaster/centos-binary-heat-api/blobs/sha256:b84e07faf72d1581aff50907b7ae59a6a98fefcfacf69714ab83e9248c999251 HTTP/1.1" 404 - "-" "python-requests/2.21.0"
192.168.24.1 - - [20/Feb/2019:00:36:48 +0000] "HEAD /v2/tripleomaster/centos-binary-heat-api/blobs/sha256:36198514f16bc5c8bac0b6c89be92bab49e3999b536ac06ba26f7c823cb5f5c8 HTTP/1.1" 200 - "-" "python-requests/2.21.0"
192.168.24.1 - - [20/Feb/2019:00:36:48 +0000] "HEAD /v2/tripleomaster/centos-binary-heat-api/blobs/sha256:b84e07faf72d1581aff50907b7ae59a6a98fefcfacf69714ab83e9248c999251 HTTP/1.1" 404 - "-" "python-requests/2.21.0"

The blob "b84e07faf72d1581aff50907b7ae59a6a98fefcfacf69714ab83e9248c999251" isn't found.
What is weird is that it doesn't show up in error logs (but access) nor in /var/log/tripleo-container-image-prepare.log on this case.