[openstack-dev] [TripleO] container-to-container-upgrades CI job and tripleo-common versions
aschultz at redhat.com
Thu May 3 15:06:30 UTC 2018
On Thu, May 3, 2018 at 8:29 AM, John Fulton <johfulto at redhat.com> wrote:
> We hit a bug  in CI job container-to-container-upgrades because a
> workflow that was needed only for Pike and Queens was removed  as
> clean up for the migration to external_deploy_tasks.
> As we need to support an n undercloud deploying an n-1 overcloud and
> then upgrading it to an n overcloud, the CI job deploys with Queens
> THT and master tripleo-common. I take this to be by design as per this
> support requirement.
I think we've always had to support this for mixed version installs.
We need to be able to manage n-1 with the latest undercloud bits. So
it does seem that tripleo-common needs to continue to be backwards
compatible for one release. So let's restore the workflow and get an
upgrade job in place so we can detect these types of breakages.
Alternatively perhaps we need an n-1 deployment on a the latest
> An implication of this is that we need to keep tripleo-common
> backwards compatible for the n-1 release and thus we couldn't delete
> this workflow until Stein.
> An alternative is to require that tripleo-common be of the same
> version as tripleo-heat-templates.
> PS: for the sake of getting CI I think we should restore the workflow
> for now 
>  https://bugs.launchpad.net/tripleo/+bug/1768116
>  https://review.openstack.org/#/c/563047
>  https://review.openstack.org/#/c/565580
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev