Bug 2216686 - Unable to pull rhosp-beta/openstack-ovn-bgp-agent image [NEEDINFO]
Summary: Unable to pull rhosp-beta/openstack-ovn-bgp-agent image
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: releng
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: Entitlement Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-22 08:47 UTC by Jun Ishii
Modified: 2023-08-03 15:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-29 14:18:34 UTC
Target Upstream Version:
Embargoed:
ifrangs: needinfo? (rhos-maint)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CWFHEALTH-2129 0 None None None 2023-06-23 14:56:22 UTC
Red Hat Issue Tracker OSP-25970 0 None None None 2023-06-22 08:48:52 UTC

Description Jun Ishii 2023-06-22 08:47:45 UTC
Description of problem:

While testing RHOSP17.1 beta, undercloud install fails due to rhosp-beta/openstack-ovn-bgp-agent container manifest does not exist.
Any of tag/version listed in container catalog does not work.

# podman pull registry.redhat.io/rhosp-rhel9/openstack-ovn-bgp-agent:latest
Trying to pull registry.redhat.io/rhosp-rhel9/openstack-ovn-bgp-agent:latest...
WARN[0002] Failed, retrying in 1s ... (1/3). Error: initializing source docker://registry.redhat.io/rhosp-rhel9/openstack-ovn-bgp-agent:latest: reading manifest latest in registry.redhat.io/rhosp-rhel9/openstack-ovn-bgp-agent: unsupported: This repository does not use the "latest" tag to track the most recent image and must be pulled with an explicit version or image reference. For more information, see: https://access.redhat.com/articles/4301321
# podman pull registry.redhat.io/rhosp-beta/openstack-ovn-bgp-agent:17.0
Trying to pull registry.redhat.io/rhosp-beta/openstack-ovn-bgp-agent:17.0...
WARN[0001] Failed, retrying in 1s ... (1/3). Error: initializing source docker://registry.redhat.io/rhosp-beta/openstack-ovn-bgp-agent:17.0: reading manifest 17.0 in registry.redhat.io/rhosp-beta/openstack-ovn-bgp-agent: unknown: Not Found
# podman pull registry.redhat.io/rhosp-beta/openstack-ovn-bgp-agent:17.0.0-33
Trying to pull registry.redhat.io/rhosp-beta/openstack-ovn-bgp-agent:17.0.0-33...
WARN[0001] Failed, retrying in 1s ... (1/3). Error: initializing source docker://registry.redhat.io/rhosp-beta/openstack-ovn-bgp-agent:17.0.0-33: reading manifest 17.0.0-33 in registry.redhat.io/rhosp-beta/openstack-ovn-bgp-agent: unknown: Not Found



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


How reproducible:
Everytime

Steps to Reproduce:
1. podman pull registry.redhat.io/rhosp-beta/openstack-ovn-bgp-agent
2.
3.

Actual results:
manifest not found

Expected results:
container image downloaded successfully

Additional info:

Comment 1 Miguel Garcia 2023-06-29 14:18:34 UTC
There was an issue with the Beta push which had gone unnoticed. It's resolved now, and the image is available here:

$ podman pull registry.redhat.io/rhosp-beta/openstack-ovn-bgp-agent-rhel9:17.1
Trying to pull registry.redhat.io/rhosp-beta/openstack-ovn-bgp-agent-rhel9:17.1...
Getting image source signatures
Checking if image destination supports signatures
Copying blob 4bfd92e814ab done  
Copying blob ca1636478fe5 skipped: already exists  
Copying blob 3bf282e4a9f3 done  
Copying config e196bcdaa6 done  
Writing manifest to image destination
Storing signatures
e196bcdaa63437eeb6389cd55233b9c3269885c32c398d43f16f2a2491418d2b

Note the path is slightly different compared to other images part of the 17.1 Beta set, as it includes the -rhel9 suffix. This is consistent with how the old 17.0 Beta was delivered.

It make take the Ecosystem Catalog [1] a few minutes to update and display it, but the container image can be pulled and consumed right now.

[1] https://catalog.redhat.com/software/containers/detail/62f3ce278c2137a6fb68b3e2


Note You need to log in before you can comment on or make changes to this bug.