Bug 1919445
| Summary: | "openstack tripleo container image list" adds extra "tags" to path causing 404 errors | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Cody Swanson <cswanson> | ||||||
| Component: | openstack-tripleo-common | Assignee: | Alex Schultz <aschultz> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | David Rosenfeld <drosenfe> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 16.1 (Train) | CC: | aschultz, hbrock, jamsmith, jslagle, mburns, mvalsecc, slinaber | ||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | tripleo-ansible-0.5.1-1.20210319143514.902c3c8.el8ost openstack-tripleo-common-11.4.1-1.20210319144626.75bd92a.el8ost | Doc Type: | Bug Fix | ||||||
| Doc Text: |
This update modifies the registry metadata creator to handle containers with and without namespaces in their URI. On the undercloud you can now manage containers that comply with the following formats:
+
undercloud_host:port/namespace/container:tag
undercloud_host:port/container:tag
+
Red Hat does not support more complex namespaces, such as undercloud_host:port/name/space/container:tag, when pushing to the undercloud.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2021-05-26 13:50:38 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Cody Swanson
2021-01-22 20:47:58 UTC
Created attachment 1749877 [details]
file list of the /var/lib/image-serve directory on the undercloud.
Created attachment 1749879 [details]
"openstack --debug tripleo container image list" command output
Please provide the container-image-prepare.yaml used during the installation. The namespace configuration is bad. namespace: rhss.dev.com:5000 It usually includes something like rhosp-rhel8. namespace: rhss.dev.com:5000/rhosp-rhel8 We use the / split names since the namespace is missing the namespace and only provides the host, the container urls end up incorrect. Given this is a satellite server, both namespace and ceph namespace(s) should likely have a namespace included with the host. So I believe this is an issue with assumptions we've made around containers always having a / separating namespace and container name. Under satellite server we do not have an normal namespace as it's just host/containername:tag rather than host/namespace/containername:tag. The image list is empty when you query it having used push_destination: true and installing the undercloud, while querying the catalog returns the extra directories. At this time, I don't think the `openstack tripleo container image` CRUD commands will work with satellite sourced images. Is this preventing a deployment? If so I would recommend dropping push_destination: true and just using the satellite as the source the deployment across the board. We'd have to figure out how to fix the image-serve to understand containers that don't have an actual namespace. If it's not breaking deployment, I think we just need to document that you can't use `openstack tripleo container image list` to see the undercloud container registry's contents of satellite sourced containers. I think I have a way to fix the catalog. It'll be a bit before it can make it back to 16.1. Please let me know if this is actually causing failures or if it's just related to the cli commands. *** Bug 1952738 has been marked as a duplicate of this bug. *** 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 16.1.6 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-2021:2097 |