Error when tagging cinder-backup container for Pacemaker

Bug #1802511 reported by Emilien Macchi on 2018-11-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Emilien Macchi

Bug Description

It seems like we broke scenario001 and 002 with - where cinder-backup container isn't found when we try to push a tag for Pacemaker:

fatal: [centos-7-inap-mtl01-0000334308]: FAILED! => {"changed": true, "cmd": "docker tag", "delta": "0:00:00.031334", "end": "2018-11-05 16:45:13.277874", "msg": "non-zero return code", "rc": 1, "start": "2018-11-05 16:45:13.246540", "stderr": "Error response from daemon: no such id:", "stderr_lines": ["Error response from daemon: no such id:"], "stdout": "", "stdout_lines": []}

Dan Prince (dan-prince) wrote :

One idea. I don't believe the new "Ansible tag" role does a pull before it tries to tag things. As such we are inherently relying on to pull images for us ahead of time as this runs early. This works for most services fine I think but note that optimizes the config runs and collectively runs the config generation for some services. I believe Cinder is one of them.

So the fix here might be to have the tagging operation pull the image ahead of time?

Fix proposed to branch: master

Changed in tripleo:
status: Triaged → In Progress

Submitter: Zuul
Branch: master

commit 7370ca76aafad52d75ab84655e7ee7c98e41002d
Author: Emilien Macchi <email address hidden>
Date: Fri Nov 9 08:53:09 2018 -0500

    tripleo-container-tag: pull image before tagging

    Adding a container pull before the tagging operation so we are sure that
    the image is in the local registry.

    We were relying on script to perform the pull but now
    we do the tag with Ansible, it's safer to ensure that the image is here.

    This patch runs a container pull before the container tag command.
    It works with both podman & docker since we use container_cli.

    Change-Id: Ib9d4ae9c2b415e427deb4b0cfc441febaa210f77
    Closes-Bug: #1802511

Changed in tripleo:
status: In Progress → Fix Released

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers