Bug 2265697 - at compute node openstack-neutron-openvswitch-agent container is pulled always from registry.redhat.io despite undercloud fetch it
Summary: at compute node openstack-neutron-openvswitch-agent container is pulled alway...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: z3
: 17.1
Assignee: Rabi Mishra
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-23 17:51 UTC by alisci
Modified: 2024-05-22 20:40 UTC (History)
11 users (show)

Fixed In Version: openstack-tripleo-common-15.4.1-17.1.20230927010820.el9ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-05-22 20:40:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-31497 0 None None None 2024-02-23 17:54:12 UTC
Red Hat Product Errata RHBA-2024:2741 0 None None None 2024-05-22 20:40:54 UTC

Internal Links: 2267924

Description alisci 2024-02-23 17:51:28 UTC
Description of problem:

a new deployment is always failing at compute node; while other container behave as expected and are fetched from undercloud, openstack-neutron-openvswitch-agent container get fetched directly from registry.redhat.io and compute node doesn't have internet connection

- pulling manually openstack-neutron-openvswitch-agent from undercloud works, however at deploy it is trying to get pulled from registry.redhat.io anyway

more details the the next private comments


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


Actual results:
openstack-neutron-openvswitch-agent container is pulled from registry.redhat.io


Expected results:
openstack-neutron-openvswitch-agent container get pulled from undercloud

Comment 27 errata-xmlrpc 2024-05-22 20:40:51 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 (Red Hat OpenStack Platform 17.1.3 bug fix and enhancement 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-2024:2741


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