openshift CI job (scenario009) fails due to missing images

Bug #1809895 reported by Martin André
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Martin André

Bug Description

Due to missing images in the local registry, tripleo-ci-centos-7-scenario009-multinode-oooq fails with the following error:

TASK [openshift_cluster_monitoring_operator : Wait for the ServiceMonitor CRD to be created] ***
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (30 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (29 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (28 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (27 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (26 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (25 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (24 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (23 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (22 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (21 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (20 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (19 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (18 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (17 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (16 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (15 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (14 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (13 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (12 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (11 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (10 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (9 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (8 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (7 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (6 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (5 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (4 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (3 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (2 retries left).
FAILED - RETRYING: Wait for the ServiceMonitor CRD to be created (1 retries left).

http://logs.openstack.org/65/613165/15/check/tripleo-ci-centos-7-scenario009-multinode-oooq/2221715/logs/undercloud/var/lib/mistral/overcloud/openshift/playbook.log.txt.gz

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (master)

Fix proposed to branch: master
Review: https://review.openstack.org/627527

Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (master)

Reviewed: https://review.openstack.org/627527
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=cf3cd200d5569fc1c217ccabbc8599df4caf957e
Submitter: Zuul
Branch: master

commit cf3cd200d5569fc1c217ccabbc8599df4caf957e
Author: Martin André <email address hidden>
Date: Wed Dec 26 22:36:59 2018 +0100

    Fix tags for openshift images

    The latest published image for cluster-monitoring-operator (v0.1.1) has
    hardcoded tags for prometheus-config-reloader and prometheus-operator
    images [1] that doesn't match the ones we set in tripleo.

    In turn, prometheus-operator v0.23.2 requires specific version of
    different images. This commit updates all image tags to a combination
    that works out of the box.

    [1] https://github.com/openshift/cluster-monitoring-operator/blob/v0.1.1/assets/prometheus-operator/deployment.yaml

    Closes-Bug: #1809895
    Change-Id: Ieea6d328d985199605f7d8b5cc654c011110621c

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (stable/rocky)

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/628371

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (stable/rocky)

Reviewed: https://review.openstack.org/628371
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=6fc7e1bf730154a4998bed96dac0814b913280c8
Submitter: Zuul
Branch: stable/rocky

commit 6fc7e1bf730154a4998bed96dac0814b913280c8
Author: Martin André <email address hidden>
Date: Wed Dec 26 22:36:59 2018 +0100

    Fix tags for openshift images

    The latest published image for cluster-monitoring-operator (v0.1.1) has
    hardcoded tags for prometheus-config-reloader and prometheus-operator
    images [1] that doesn't match the ones we set in tripleo.

    In turn, prometheus-operator v0.23.2 requires specific version of
    different images. This commit updates all image tags to a combination
    that works out of the box.

    [1] https://github.com/openshift/cluster-monitoring-operator/blob/v0.1.1/assets/prometheus-operator/deployment.yaml

    Closes-Bug: #1809895
    Change-Id: Ieea6d328d985199605f7d8b5cc654c011110621c
    (cherry picked from commit cf3cd200d5569fc1c217ccabbc8599df4caf957e)

tags: added: in-stable-rocky
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 10.3.0

This issue was fixed in the openstack/tripleo-common 10.3.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 9.5.0

This issue was fixed in the openstack/tripleo-common 9.5.0 release.

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.