Browse Source

Do not rely on defaults for DockerCephDaemonImage in CI.

When using mixed-versions deployment, as
it's the case for upgrades CI jobs. The
docker image version is being set by the
undercloud's tripleo-common package release.

As the undercloud is one release over the
overcloud, we end up deploying next's release
ceph docker image (ceph luminous in pike). By
setting the DockerCephDaemon parameter to the
right ceph docker image version we ensure that
the right version is being deployed

Closes-Bug: #1767329
Change-Id: Iff84601195722429f0e31334fee4845da0ca549c
tags/7.0.14
Jose Luis Franco Arza 1 year ago
parent
commit
2889670370

+ 1
- 0
ci/environments/scenario001-multinode-containers.yaml View File

@@ -113,6 +113,7 @@ parameter_defaults:
113 113
   ManagePolling: true
114 114
 
115 115
   Debug: true
116
+  DockerCephDaemonImage: docker.io/ceph/daemon:v3.0.3-stable-3.0-jewel-centos-7-x86_64
116 117
   CephAnsibleDisksConfig:
117 118
     devices:
118 119
       - /dev/loop3

+ 1
- 0
ci/environments/scenario004-multinode-containers.yaml View File

@@ -93,6 +93,7 @@ parameter_defaults:
93 93
     nova::compute::libvirt::services::libvirt_virt_type: qemu
94 94
     nova::compute::libvirt::libvirt_virt_type: qemu
95 95
   Debug: true
96
+  DockerCephDaemonImage: docker.io/ceph/daemon:v3.0.3-stable-3.0-jewel-centos-7-x86_64
96 97
   CephAnsibleDisksConfig:
97 98
     devices:
98 99
       - /dev/loop3

Loading…
Cancel
Save