![Jiri Stransky](/assets/img/avatar_default.png)
Non-working containers upgrade CI is caused by the fact that all multinode jobs deploy pacemaker environments. Currently we cannot upgrade Pacemakerized deployments anyway (containerization of pacemakerized services is WIP), upgrades have only been tested with non-Pacemaker deployments so far. We need a new environment which will not try deploying in a pacemakerized way. When pacemaker-managed services are containerized, we can change the job to upgrade an HA deployment (or single-node "HA" at least), and perhaps even get rid of the environment file introduced here, and reuse multinode.yaml. Change-Id: Ie635b1b3a0b91ed5305f38d3c76f6a961efc1d30 Closes-Bug: #1682051
TripleO CI environments
TripleO CI environments are exclusively used for Continuous Integration purpose or for development usage. They should not be used in production and we don't guarantee they work outside TripleO CI.
For more informations about TripleO CI, please look: https://github.com/openstack-infra/tripleo-ci