The docker image docker.io/starlingx/stx-pci-irq-affinity-agent:master-centos-stable-20220301T054136Z.0 cannot be pulled

Bug #1962742 reported by Bogdan-Iulian Andrei
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
Critical
Scott Little

Bug Description

Brief Description
-----------------
The docker image docker.io/starlingx/stx-pci-irq-affinity-agent:master-centos-stable-20220301T054136Z.0 cannot be pulled.
$ docker pull docker.io/starlingx/stx-pci-irq-affinity-agent:master-centos-stable-20220301T054136Z.0
Error response from daemon: manifest for starlingx/stx-pci-irq-affinity-agent:master-centos-stable-20220301T054136Z.0 not found: manifest unknown: manifest unknown

Severity
--------
<Critical: System/Feature is not usable due to the defect>

Steps to Reproduce
------------------
Try to pull the docker image docker.io/starlingx/stx-pci-irq-affinity-agent:master-centos-stable-20220301T054136Z.0

Expected Behavior
------------------
All docker images should be available.

Actual Behavior
----------------
I cannot pull this image.

Reproducibility
---------------
100% reproducible

System Configuration
--------------------
All configurations

Branch/Pull Time/Commit
-----------------------
master

Last Pass
---------
20220301T034837Z

Timestamp/Logs
--------------
Will be attached.

Test Activity
-------------
Sanity

Workaround
----------
-

Revision history for this message
Bogdan-Iulian Andrei (bandrei) wrote :
Revision history for this message
Ghada Khalil (gkhalil) wrote :

screening: stx.7.0 / critical - this is causing a red sanity.
Report: http://lists.starlingx.io/pipermail/starlingx-discuss/2022-March/012816.html

Changed in starlingx:
importance: Undecided → Critical
tags: added: stx.7.0 stx.sanity
Revision history for this message
Davlet Panech (dpanech) wrote :

Looks like a transient error with Docker Hub. A subsequent build from Mar 2nd worked, ie

starlingx/stx-pci-irq-affinity-agent:master-centos-stable-20220302T080008Z.0

exists in Docker Hub.

Please re-test the Mar 2 build.

Ghada Khalil (gkhalil)
tags: added: stx.build
Changed in starlingx:
status: New → Triaged
Revision history for this message
Scott Little (slittle1) wrote :

Jenkins build on CENGN failed to push two tags to docker.io. The error message was

    unexpected HTTP status: 500 Internal Server Error

The retry loop eventually gave up.

Our ability to push to docker.io was restored in the next build.

The main issue I see here is that 'build-stx-images.sh ... push' doesn't return an error code when the image builds ok, but the push fails. Without that, jenkins didn't realize the overall build had failed.

Revision history for this message
Ghada Khalil (gkhalil) wrote (last edit ):

Marking as Fix Released based on Scott's comments above that this was addressed in a follow-up build.

Please retry sanity

Changed in starlingx:
status: Triaged → Fix Released
assignee: nobody → Scott Little (slittle1)
Revision history for this message
Ghada Khalil (gkhalil) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.