Bug 1791784
| Summary: | OSP 16 beta fails when performing an authenticated pull from registry.redhat.io | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Brian J. Atkisson <batkisso> | ||||
| Component: | openstack-tripleo-common | Assignee: | Alex Schultz <aschultz> | ||||
| Status: | CLOSED ERRATA | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 16.0 (Train) | CC: | aschultz, augol, emacchi, hbrock, jschluet, jslagle, juvillar, mburns, mchappel, slinaber | ||||
| Target Milestone: | beta | Keywords: | Reopened, Triaged | ||||
| Target Release: | 16.1 (Train on RHEL 8.2) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | openstack-tripleo-common-11.3.3-0.20200302223724.1e95c34.el8ost | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-07-29 07:50:33 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: | |||||||
| Bug Depends On: | 1792486 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Brian J. Atkisson
2020-01-16 13:20:52 UTC
FYI, tried again with: openstack-tripleo-common noarch 11.3.3-0.20200107225621.47626e1.el8ost openstack-beta-for-rhel-8-x86_64-rpms 99 k python3-paunch noarch 5.3.1-0.20191214120154.b2f3c3c.el8ost openstack-beta-for-rhel-8-x86_64-rpms 58 k paunch-services noarch 5.3.1-0.20191214120154.b2f3c3c.el8ost openstack-beta-for-rhel-8-x86_64-rpms 17 k openstack-tripleo-heat-templates noarch 11.3.2-0.20200109050651.8f93d27.el8ost openstack-beta-for-rhel-8-x86_64-rpms 570 k openstack-tripleo-common-containers noarch 11.3.3-0.20200107225621.47626e1.el8ost openstack-beta-for-rhel-8-x86_64-rpms 37 k tripleo-ansible noarch 0.4.2-0.20200110023759.ee731ba.el8ost openstack-beta-for-rhel-8-x86_64-rpms 230 k puppet-tripleo noarch 11.4.1-0.20200106153547.5946c6f.el8ost openstack-beta-for-rhel-8-x86_64-rpms 278 k python3-tripleoclient noarch 12.3.1-0.20191230195937.585fb28.el8ost openstack-beta-for-rhel-8-x86_64-rpms 488 k python3-tripleo-common noarch 11.3.3-0.20200107225621.47626e1.el8ost openstack-beta-for-rhel-8-x86_64-rpms 294 k python3-novajoin noarch 1.3.0-0.20191217200124.265146e.el8ost openstack-beta-for-rhel-8-x86_64-rpms 109 k python3-tripleoclient-heat-installer noarch 12.3.1-0.20191230195937.585fb28.el8ost openstack-beta-for-rhel-8-x86_64-rpms 11 k And it failed again with the Jan. 16 updates above. The 401 is misleading here. The issue is that it is trying to fetch the GA containers which have not been published yet. Prior to GA, a custom file providing the beta container information must be used when deploying the undercloud. Did you specify the container_images_file = /home/stack/containers-prepare-parameter.yaml So I attempted to reproduce this error with the beta and a beta containers-prepare-parameter.yaml specified for container_images_file in undercloud.conf. It didn't reproduce so I believe the issue is what I previously described where the file wasn't configured so when the install ran it attempt to pull the production containers which do not currently exist. I've proposed a bug upstream to address the error messaging around this in the future and we'll get that backported back into in a future 16 point release. If you can reproduce this with a container_images_file in undercloud.conf, please provide the undercloud.conf and the yaml file and we'll look into that further. I'll be re-purposing this bug track the error message improvements. Created attachment 1652981 [details]
undercloud.conf
We *have* added container_images_file. It works fine if we provide a private registry.
I've figured it out. So if you do not specify a push_destination in the ContainerImagePrepare, you need to also specify ContainerImageRegistryLogin: true in order to have the login actually performed on the various systems. This is missing from the documentation. If you have push_destination set, we will login as part of our collection of containers to push to the undercloud registry when this is run on the undercloud during the undercloud/overcloud deployments. The docs bz is 1792486 Adding "ContainerImageRegistryLogin: true" appears to have worked for us. (In reply to Alex Schultz from comment #7) > I've figured it out. So if you do not specify a push_destination in the > ContainerImagePrepare, you need to also specify ContainerImageRegistryLogin: > true in order to have the login actually performed on the various systems. > This is missing from the documentation. If you have push_destination set, > we will login as part of our collection of containers to push to the > undercloud registry when this is run on the undercloud during the > undercloud/overcloud deployments. Hrm, can you add an example of a working containers-prepare-parameter.yaml file? I tried adding ContainerImageRegistryLogin to a few places in the file with no luck. Thanks! parameter_defaults:
ContainerImagePrepare:
- set:
ceph_alertmanager_image: alertmanager
ceph_alertmanager_namespace: docker.io/prom
ceph_alertmanager_tag: v0.16.2
ceph_grafana_image: grafana
ceph_grafana_namespace: docker.io/grafana
ceph_grafana_tag: 5.2.4
ceph_image: rhceph-4.0-rhel8
ceph_namespace: docker-registry.upshift.redhat.com/ceph
ceph_node_exporter_image: node-exporter
ceph_node_exporter_namespace: docker.io/prom
ceph_node_exporter_tag: v0.17.0
ceph_prometheus_image: prometheus
ceph_prometheus_namespace: docker.io/prom
ceph_prometheus_tag: v2.7.2
ceph_tag: latest
name_prefix: openstack-
name_suffix: ''
namespace: registry.redhat.io/rhosp-beta
#namespace: registry.redhat.io/rhosp16
neutron_driver: ovn
rhel_containers: false
tag: latest
tag_from_label: '{version}-{release}'
ContainerImageRegistryLogin: true
ContainerImageRegistryCredentials:
registry.redhat.io:
'username': 'password'
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/RHBA-2020:3148 |