container deploy (partly) ignores local registry

Bug #1700032 reported by Matthias Runge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Invalid
High
Unassigned

Bug Description

I have a setup, where only the undercloud can reach the external network. During container deploy, like described here: https://docs.openstack.org/developer/tripleo-docs/containers_deployment/overcloud.html#deploying-the-containerized-overcloud

I got
.....
"Trying to pull repository docker.io/tripleoupstream/centos-binary-panko-api ... ", "Pulling repository docker.io/tripleoupstream/centos-binary-panko-api", "/usr/bin/docker-current: Network timed out while trying to connect to https://index.docker.io/v1/repositories/tripleoupstream/centos-binary-panko-api/images. You may want to check your internet connection or if you are behind a proxy..", "See '/usr/bin/docker-current run --help'.", "", "2017-06-21 05:46:54,420 ERROR: Failed running docker-puppet.py for panko", "2017-06-21 05:46:54,421 DEBUG: config_volume gnocchi", "2017-06-21 05:46:54,421 DEBUG: puppet_tags file,file_line,concat,augeas,gnocchi_api_paste_ini,gnocchi_config,gnocchi_config,gnocchi_config", "2017-06-21 05:46:54,421 DEBUG: manifest include ::tripleo::profile::base::gnocchi::api", "", "include ::tripleo::profile::base::gnocchi::metricd", "", "include ::tripleo::profile::base::gnocchi::statsd", "", "2017-06-21 05:46:54,421 DEBUG: config_image tripleoupstream/centos-binary-gnocchi-api:latest", "2017-06-21 05:46:54,421 DEBUG: volumes []",
....

Tags: containers
Matthias Runge (mrunge)
tags: added: containers
Changed in tripleo:
status: New → Triaged
importance: Undecided → High
milestone: none → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Revision history for this message
Steven Hardy (shardy) wrote :

Can you please confirm if this is still an issue with the new prepare/upload workflow, and if so please provide the exact commands used and a copy of the environment files?

I have seen that docker config changes (which we don't currently expose via tripleo) are required if you want to ensure you can never pull from docker.io, but if the correct environment files are used we should prefer the local registry I think so more info needed to reproduce.

Changed in tripleo:
milestone: pike-rc1 → pike-rc2
Changed in tripleo:
milestone: pike-rc2 → queens-1
Revision history for this message
Matthias Runge (mrunge) wrote :

I can not reproduce this anymore.

Revision history for this message
Martin André (mandre) wrote :

Possibly related to bug #1715136. We've implemented retry loops in docker-puppet.py and in the upload command to accommodate with occasional docker I/O issues.
I'm closing this bug, please reopen if it reappears.

Changed in tripleo:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.