Looking at the build logs, it looks like there may have been a brief service issue with the docker hub during the build, as the push ultimately failed with "received unexpected HTTP status: 503 Service Unavailable": http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docke... This error isn't caught by the build-stx-images.sh, so we'll need to update the tool to catch this in the future and add retries. This build was an on-demand one, and we do have a build from earlier in the day. There likely would be no churn against this earlier master-centos-stable-20210415T022926Z.0 image, so I could retag that to unblock you here? From: Dimofte, Alexandru <alexandru.dimofte@intel.com> Sent: Friday, April 16, 2021 9:44 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Failed to download image docker.io/starlingx/stx-neutron:master-centos-stable-20210415T134403Z.0 [Please note: This e-mail is from an EXTERNAL e-mail address] Hi guys, I see this issue trying to pull the stx-neutron image. $ docker pull docker.io/starlingx/stx-neutron:master-centos-stable-20210415T134403Z.0 Error response from daemon: manifest for starlingx/stx-neutron:master-centos-stable-20210415T134403Z.0 not found: manifest unknown: manifest unknown sys_stxval@kasstxj:/localdisk/starlingx/watcher/mirror_scripts$ Is this a known problem? Kind regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte@intel.com<mailto:alexandru.dimofte@intel.com> Intel Romania
