subsequent updates of config

This commit is contained in:
Felix Kunde 2020-04-20 15:05:05 +02:00
parent 2c194e7a74
commit 04a67641ab
1 changed files with 9 additions and 2 deletions

View File

@ -215,10 +215,17 @@ class EndToEndTestCase(unittest.TestCase):
cluster_label = 'application=spilo,cluster-name=acid-minimal-cluster'
# enable lazy update
patch_lazy_spilo_upgrade = {
"data": {
"enable_lazy_spilo_upgrade": "true"
}
}
k8s.update_config(patch_lazy_spilo_upgrade)
# update docker image in config which usually triggers a rolling update
conf_image = "registry.opensource.zalan.do/acid/spilo-cdp-12:1.6-p111"
patch_lazy_spilo_upgrade = {
"data": {
"enable_lazy_spilo_upgrade": "true",
"docker_image": conf_image
}
}
@ -236,7 +243,7 @@ class EndToEndTestCase(unittest.TestCase):
# sanity check: restarted pod runs the image specified in operator's conf
new_image = k8s.get_effective_pod_image(replica_pod)
self.assertEqual(conf_image, new_image,
self.assertEqual(new_image, conf_image
"Lazy upgrade failed: restarted pod {} runs image {} different from the one in operator conf {}".format(replica_pod, new_image, conf_image))
# lazy update works if the restarted pod and older pods have different Spilo versions