scenarios in Ocata reference services introduced in Pike

Bug #1708014 reported by Emilien Macchi on 2017-08-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Critical
Jiří Stránský

Bug Description

Jobs which test upgrades from baremetal to containerized environments fail because they don't deploy TripleO from Ocata but from Pike (master).

See http://logs.openstack.org/10/489710/1/experimental/gate-tripleo-ci-centos-7-scenario001-multinode-oooq-container-upgrades/b83b740/logs/undercloud/home/jenkins/overcloud_deploy.log.txt.gz#_2017-08-01_19_56_30

See: https://github.com/openstack/tripleo-heat-templates/blob/master/ci/environments/scenario001-multinode-containers.yaml#L16
Which is on master, but not on stable/ocata of course.

We need to change the tooling to deploy THT from stable/ocata and then upgrade it to Pike.
Right now, we have zero testing for upgrades from Ocata to Pike that actually work when deploying in containers.

Changed in tripleo:
milestone: none → pike-rc1
tags: added: ci
tags: added: quickstart upgrade

The job doesn't deploy pike, it deploys ocata:

http://logs.openstack.org/10/489710/1/experimental/gate-tripleo-ci-centos-7-scenario001-multinode-oooq-container-upgrades/b83b740/console.html#_2017-08-01_19_12_14_388824

Problem is that the ocata version of the scenario includes congress too.

summary: - multinode-oooq-container-upgrades deploys master instead of stable
+ scenario001 upgrade job tries to deploy Congress on Ocata
Jiří Stránský (jistr) wrote :

Actually more precisely, the container scenarios were backported 1-1, so they try to reference docker services, which won't work :)

summary: - scenario001 upgrade job tries to deploy Congress on Ocata
+ scenarios in Ocata reference services introduced in Pike
Changed in tripleo:
assignee: nobody → Jiří Stránský (jistr)
tags: removed: alert
tags: removed: quickstart
Changed in tripleo:
status: Triaged → In Progress

Reviewed: https://review.openstack.org/489874
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=14406f8f7ccd7c21b13f70f7a3a6039db3464ad8
Submitter: Jenkins
Branch: stable/ocata

commit 14406f8f7ccd7c21b13f70f7a3a6039db3464ad8
Author: Jiri Stransky <email address hidden>
Date: Wed Aug 2 08:26:23 2017 +0200

    Remove docker references from stable/ocata scenarios.

    The container scenarios referenced dockerized services, which doesn't
    make sense in Ocata. In Ocata, these scenarios should be normal puppet
    deployments, but without HA, until we start CI-ing HA upgrades.

    Change-Id: I29675e304ed0e7cd7d666570d9af30ad95ba7caf
    Closes-Bug: #1708014

tags: added: in-stable-ocata
Changed in tripleo:
milestone: pike-rc1 → pike-rc2
Changed in tripleo:
status: In Progress → Fix Released

This issue was fixed in the openstack/tripleo-heat-templates 6.2.1 release.

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

Other bug subscribers