Bug 1485400
Summary: | overcloud container image upload fails due to missing containers | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Dan Prince <dprince> |
Component: | openstack-tripleo-common | Assignee: | Dan Prince <dprince> |
Status: | CLOSED ERRATA | QA Contact: | Alexander Chuzhoy <sasha> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 12.0 (Pike) | CC: | adhingra, jjoyce, jschluet, m.andre, mburns, ohochman, sbaker, slinaber |
Target Milestone: | beta | Keywords: | Triaged |
Target Release: | 12.0 (Pike) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-common-7.6.3-0.20171010234828.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-13 21:58:11 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: |
Description
Dan Prince
2017-08-25 14:58:34 UTC
Looks like the container images for congress, barbican, and tacker are all missing and as such the 'container images upload' command files. In the example I had above I had to manually update the generated images_files.yaml file like this to get it to pass. [root@undercloud-0 ~]# diff images_file.yaml.orig images_file.yaml 14,16c14,16 < - imagename: rhosp12/openstack-barbican-api-docker:2017-08-18.2 < pull_source: docker-registry.engineering.redhat.com < push_destination: 172.19.0.3:8787 --- > #- imagename: rhosp12/openstack-barbican-api-docker:2017-08-18.2 > #pull_source: docker-registry.engineering.redhat.com > #push_destination: 172.19.0.3:8787 44,46c44,46 < - imagename: rhosp12/openstack-congress-api-docker:2017-08-18.2 < pull_source: docker-registry.engineering.redhat.com < push_destination: 172.19.0.3:8787 --- > #- imagename: rhosp12/openstack-congress-api-docker:2017-08-18.2 > #pull_source: docker-registry.engineering.redhat.com > #push_destination: 172.19.0.3:8787 245,247c245,247 < - imagename: rhosp12/openstack-tacker-docker:2017-08-18.2 < pull_source: docker-registry.engineering.redhat.com < push_destination: 172.19.0.3:8787 --- > #- imagename: rhosp12/openstack-tacker-docker:2017-08-18.2 > #pull_source: docker-registry.engineering.redhat.com > #push_destination: 172.19.0.3:8787 Jon: could you confirm that we aren't releasing barbican, tacker, and congress containers at this time. And if not should we perhaps put in a patch to exclude these from our 'image prepare' templates? The prepare command has the following options for filtering entries: --exclude <regex> Pattern to match against resulting imagename entries to exclude from the final output. Can be specified multiple times. --service-environment-file <file path>, -e <file path> Environment files specifying which services are containerized. Entries will be filtered to only contain images used by containerized services. (Can be specified more than once.) But also I think there is a good case for downstream carrying a patch against tripleo-common/container-images/overcloud_containers.yaml.j2 to remove entries for images which downstream does not support. (In reply to Dan Prince from comment #2) > Jon: could you confirm that we aren't releasing barbican, tacker, and > congress containers at this time. And if not should we perhaps put in a > patch to exclude these from our 'image prepare' templates? That is correct for OSP 12 we will not be packaging and shipping taker, barbican, and congress container images. Also to follow up on comment #4 yes this would probably be a good patch to carry for OSP 12. unable to reproduce with : OpenStack-12.0-RHEL-7 Puddle: 2017-10-24.3 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, 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/RHEA-2017:3462 |