stable/rocky standalone failing to pull containers from local registry

Bug #1808591 reported by Alex Schultz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Alex Schultz

Bug Description

We've recently turned on container updates in quickstart on master (https://review.openstack.org/#/c/621517/) but the stable/rocky patch to support it has not landed (https://review.openstack.org/#/c/624869/).

http://logs.openstack.org/04/624304/2/gate/tripleo-ci-centos-7-standalone/09c0a0c/logs/undercloud/home/zuul/standalone_deploy.log.txt.gz#_2018-12-14_21_09_16

2018-12-14 21:09:16 | "2018-12-14 21:07:43,587 INFO: 26011 -- Pulling image: 192.168.24.1:8787/tripleorocky/centos-binary-nova-placement-api:current-tripleo-updated-20181214204023",
2018-12-14 21:09:16 | "2018-12-14 21:07:46,619 WARNING: 26013 -- docker pull failed: Error while pulling image: Get http://192.168.24.1:8787/v1/repositories/tripleorocky/centos-binary-redis/images: dial tcp 192.168.24.1:8787: getsockopt: connection refused",
2018-12-14 21:09:16 | "2018-12-14 21:07:46,619 WARNING: 26013 -- retrying pulling image: 192.168.24.1:8787/tripleorocky/centos-binary-redis:current-tripleo-updated-20181214204023",
2018-12-14 21:09:16 | "2018-12-14 21:07:46,619 WARNING: 26012 -- docker pull failed: Error while pulling image: Get http://192.168.24.1:8787/v1/repositories/tripleorocky/centos-binary-swift-proxy-server/images: dial tcp 192.168.24.1:8787: getsockopt: connection refused",

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to tripleo-heat-templates (stable/rocky)

Reviewed: https://review.openstack.org/624869
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=c7d10a55a64e4efe967cec795c90bdd5ff55702e
Submitter: Zuul
Branch: stable/rocky

commit c7d10a55a64e4efe967cec795c90bdd5ff55702e
Author: Quique Llorente <email address hidden>
Date: Tue Dec 11 12:12:19 2018 +0100

    Run local registry and prep cont at standalone

    The standalone job were not running yum update on the containers, to do
    so we need to specify the updater paremters in the
    container-prepare-parameters [1] and also we have to activate the docker
    local registry and call the conatiner prepare service.

    [1] https://review.openstack.org/#/c/621517/

    NOTE: this change differs from master as we do not have a podman service
    in Rocky.
    Related-Bug: #1808591

    Change-Id: I74e817bc9b9dd522db3da7753c91a3884d99f8c8
    Related-Bug: #1805968
    (cherry picked from commit 62b54268af4c341288e745c356f28124f61e9d2b)

tags: added: in-stable-rocky
Changed in tripleo:
status: Triaged → Fix Released
assignee: nobody → Alex Schultz (alex-schultz)
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.