[openstack-dev] [tripleo] scenario000-multinode-oooq-container-upgrades

James Slagle james.slagle at gmail.com
Tue Jun 12 13:06:47 UTC 2018


On Mon, Jun 11, 2018 at 3:34 PM, Wesley Hayutin <whayutin at redhat.com> wrote:
> Greetings,
>
> I wanted to let everyone know that we have a keystone only deployment and
> upgrade job in check non-voting.  I'm asking everyone in TripleO to be
> mindful of this job and to help make sure it continues to pass as we move it
> from non-voting check to check and eventually gating.

+1, nice work!

> Upgrade jobs are particularly difficult to keep running successfully because
> of the complex workflow itself, job run times and other factors.  Your help
> to ensure we don't merge w/o a pass on this job will go a long way in
> helping the tripleo upgrades team.
>
> There is still work to be done here, however it's much easier to do it with
> the check non-voting job in place.

The job doesn't appear to be passing at all on stable/queens. I see
this same failure on several patches:
http://logs.openstack.org/59/571459/1/check/tripleo-ci-centos-7-scenario000-multinode-oooq-container-upgrades/8bbd827/logs/undercloud/home/zuul/overcloud_upgrade_run_Controller.log.txt.gz

Is this a known issue?

-- 
-- James Slagle
--



More information about the OpenStack-dev mailing list