[tripleo][ppc64le] Unexpected Return Code from TripleO Container Build Playbooks on ppc64le

Adam Kimball baha at linux.vnet.ibm.com
Wed Dec 4 19:56:30 UTC 2019

Hello all,

Mike Turek and I have been working to get a ppc64le job to build tripleo 
containers for quite some time now. A few weeks back, we stumbled into a 
strange issue where the containers build job was issuing a return code 
1, despite all containers successfully building. This has largely 
blocked our ability to push containers up to docker hub or report 
success through the delorean API.

We've been pushing a number of patches to expand the logging of both our 
job, and the tripleo playbooks themselves, to get a better idea of 
what's going on. The most recent was a patch to show which containers 
have python futures that have been throwing exceptions, and why. [1]

The end result of this seems to be that a number of jobs are reporting 
as incomplete. An example of this can be seen at timestamp 20:16:07 of 
an example build log. [2]

However, upon checking the list of successfully built containers [3], or 
the RDO registry itself [4], one can see that the containers producing 
job not complete errors have actually built, and are being uploaded. The 
error log generated by the tripleo playbooks is also empty. [5]

At this point, we're wondering what the path forward is. It seems like 
the issue stems from some unintended behavior in the tripleo playbooks 
themselves, not anything from our job. We're trying to figure out if 
this behavior is something that should be preventing us from reporting 
successful builds, and if so, how it can be fixed.

Adam Kimball

[1] - https://review.opendev.org/#/c/695723/
[2] - 
[3] - 
[4] - https://console.registry.rdoproject.org/registry
[5] - 

More information about the openstack-discuss mailing list