)]}' { "log": [ { "commit": "5cf1f61fbffeb901955f10469babce0b9905a093", "tree": "d0740139e6bd6023f9435c4312b84c672fdcc288", "parents": [ "cac3eefc44afca458692e9dadb539c0cb17dc9e4" ], "author": { "name": "Gregory Thiemonge", "email": "gthiemon@redhat.com", "time": "Wed Feb 03 14:34:18 2021 +0100" }, "committer": { "name": "Gregory Thiemonge", "email": "gthiemon@redhat.com", "time": "Tue Jul 20 07:17:35 2021 +0200" }, "message": "Fix two-node job configuration\n\nTwo-node job was failing because devstack tried to compile the\ntest_server.go file on controller2.\ncontroller2 doesn\u0027t have tempest installed, but octavia-tempest-plugin\nwas installed. The compilation step was failing and is not necessary\nthere.\n\nFix octavia-v2-act-stdby-dsvm-scenario-two-node definition, overrides\nwere not applied.\nFix the \"zuul_copy_output\" section.\n\nMove to ML2/OVN backend.\n\nCo-Authored-By: Carlos Goncalves \u003ccgoncalves@redhat.com\u003e\nChange-Id: I24976e93e9ea8f7f50c9da014c2627965512893c\n" }, { "commit": "7cca66d7a1373f0d7ea632390251cbf496e51a3f", "tree": "d9b31fddcb4b0b8d537c1279de7fd167d91b563f", "parents": [ "bbddf4b78d2bfe0ae15dc0d0826a11162a882fe9" ], "author": { "name": "Carlos Goncalves", "email": "cgoncalves@redhat.com", "time": "Thu Jan 16 17:50:44 2020 +0100" }, "committer": { "name": "Carlos Goncalves", "email": "cgoncalves@redhat.com", "time": "Wed Feb 19 18:56:27 2020 +0100" }, "message": "Enable KVM libvirt type on all scenario jobs\n\nA subset of nodepool providers have KVM nested virtualization enabled.\nAt present, examples are Vexxhost, OVH, FortNebula and Limestone.\n\nWe\u0027ve had a pre-run script for CI to enable KVM when running in one of\nthose providers. This has some drawbacks:\n1. With Zuul v3, DEVSTACK_GATE_LIBVIRT_TYPE is obsoleted in favor of\n LIBVIRT_TYPE in devstack_localrc.\n2. The list was outdated (e.g. Vexxhost and FortNebula were not in).\n3. Some of the nested virt friendly providers have mixed KVM/TCG\n servers.\n3. Enablement of nested virtualization would require updating of the KVM\n providers list in our side.\n\nWhen LIBVIR_TYPE\u003dKVM, devstack checks if KVM is really available (via\ndevstack/lib/nova). If it is not, it falls back to qemu (TCG). This\ncheck is available since at least Mitaka.\n\nAlso, some provider nodes expose a generic CPU model. Libvirt matches\nthe named CPU model to the closest from the host. As a result, the\nmatched one may not include the CPUID parameter which seems to be\nrequired for nested virtualization. This find-by-match (cpu_mode option\nin Nova) can be switched \"host-passthrough\" in which case will cause\nlibvirt to tell KVM to passthrough the host CPU with no modifications.\nThe disadvantage of this mode is guests can only be migrated to an\nexactly matching host CPU, but we don\u0027t need this in CI.\n\nDepends-On: https://review.opendev.org/#/c/703324/\n\nChange-Id: I6c4596aa9cc2d7f7703c5acb54fdaed97756788a\n" }, { "commit": "c2e1216e8ec8a50fd8d4ea5b7a05a0805e8b5965", "tree": "9fec32acc318c7f8b8d89b233b35f07c1d989131", "parents": [ "c9414e8419322815dc97a1919f19a44a0044c151" ], "author": { "name": "Carlos Goncalves", "email": "cgoncalves@redhat.com", "time": "Thu Feb 14 23:57:44 2019 +0100" }, "committer": { "name": "Carlos Goncalves", "email": "cgoncalves@redhat.com", "time": "Mon Apr 08 18:57:12 2019 +0200" }, "message": "Add iptables-based active/standby scenario test\n\nThis patch adds a tempest scenario test for active/standby topology.\n\nThis scenario takes a similar approach to scenario proposed in Change-Id\nIbcd5552a67cea650edc72bfaa986357267ca2407 with the difference that it\ndoes not rely on amphora stats API. Instead, it uses iptables to log VIP\ntraffic and make assertions based on logging.\n\nCo-Authored-By: Michael Johnson \u003cjohnsomor@gmail.com\u003e\n\nChange-Id: I24a6fc3387166ec6cdbd57a5ca9f63743748ec68\n" }, { "commit": "cafb606023b0c1df02272046faf76edf94793642", "tree": "cda6bd0b1a82f2301cbd24b841ef3c94c926346e", "parents": [ "b5690471c3af8826477e7f978a286afa5459bf93" ], "author": { "name": "Michael Johnson", "email": "johnsomor@gmail.com", "time": "Thu Sep 06 12:33:26 2018 -0700" }, "committer": { "name": "Michael Johnson", "email": "johnsomor@gmail.com", "time": "Fri Sep 07 15:05:37 2018 -0700" }, "message": "Disable KVM at limestone (again)\n\nThere appears to be a kernel regression that is leading to KVM failures\nagain. This patch adds limestone to the exclusion list based on job\nfailures[1].\n\n[1] http://logs.openstack.org/32/600332/3/check/octavia-v1-dsvm-scenario/ \\\n 467a1e6/logs/libvirt/qemu/instance-00000001.txt.gz\n\nChange-Id: I91782536599fc28f2824a5dcc1483be46904ce56\n" }, { "commit": "b5690471c3af8826477e7f978a286afa5459bf93", "tree": "608b3ab542dc9b2e15553a813e91e48f22f00983", "parents": [ "921ed42ff94b6f717eedcc25ea27db4f436c7d74" ], "author": { "name": "Michael Johnson", "email": "johnsomor@gmail.com", "time": "Wed Sep 05 09:20:39 2018 -0700" }, "committer": { "name": "Carlos Goncalves", "email": "cgoncalves@redhat.com", "time": "Thu Sep 06 10:36:19 2018 +0200" }, "message": "Fix the scenario parent job to use the live base\n\nThe dsvm scenario jobs was using \"octavia-dsvm-base\" parent job and\nnot the required \"octavia-dsvm-live-base\" job. This patch corrects that.\n\nIt also changes the \"octavia-v2-dsvm-scenario-centos.7\" job name to\n\"octavia-v2-dsvm-scenario-centos-7\" to comply with the naming guideline[1].\n\nThe same change is applied to the bionic job, which becomes \"-bionic\".\n\nIt also increases the job timeout for \"live\" jobs to 9,000 seconds, or\n2.5 hours to accomidate tcg gate hosts.\n\n[1] https://docs.openstack.org/infra/manual/ \\\n drivers.html#consistent-naming-for-jobs-with-zuul-v3\n\nChange-Id: I7aaa86bf0a626cbef17611445d4499969741534d\n" }, { "commit": "28f29e281cccb556693a1300db20d977fe658699", "tree": "da90c673e889e79d66fd5c0133bf6a32a4ee53ed", "parents": [ "904a4481c9d44b8c784d11d3208cc6b8492124fb" ], "author": { "name": "Michael Johnson", "email": "johnsomor@gmail.com", "time": "Sun Aug 19 13:44:42 2018 -0700" }, "committer": { "name": "Michael Johnson", "email": "johnsomor@gmail.com", "time": "Sun Aug 19 13:45:04 2018 -0700" }, "message": "Disable kvm on OVH infra instances\n\nOVH infra hosts are causing \"KVM: entry failed, hardware error 0x0\"\nfailures where instances fail to start (cirros, etc.).\nThis patch excludes OVH instances from kvm enablement until the issue is\nresolved.\n\nChange-Id: I50006cb60deef6943d95c2c04c444dccca94c8b0\n" }, { "commit": "8999651dd19787d18d4248bd06afe3b7ec544ad6", "tree": "bd33a0b069217d8188a5bf0b53029a2a463d280c", "parents": [ "74617dabff8e61c3d47e84a3c75477a72a544bf9" ], "author": { "name": "Michael Johnson", "email": "johnsomor@gmail.com", "time": "Fri Jun 29 09:34:29 2018 -0700" }, "committer": { "name": "Michael Johnson", "email": "johnsomor@gmail.com", "time": "Fri Jun 29 09:34:55 2018 -0700" }, "message": "Re-enable KVM\n\nA recent kernel update in the nodepool images has resolved the issue\nwe were seeing with using KVM on some hosting providers.\nThis patch removes the exclusion for those hosting providers and\nallows the Octavia gates to use KVM if it is available on the host.\n\nChange-Id: Ibd726a831db4988ab1820084b2683c38a852ce93\n" }, { "commit": "986e3f543c6b3c588b88b1748641680759ed2856", "tree": "97bdf98b78d98f11f678ac7ada5121ed147038f5", "parents": [ "0c90ef6972d529084b5573278cf17e93ffb3d8d2" ], "author": { "name": "Jude Cross", "email": "jcross@godaddy.com", "time": "Mon Jul 24 14:57:20 2017 -0700" }, "committer": { "name": "Michael Johnson", "email": "johnsomor@gmail.com", "time": "Tue Apr 10 12:20:01 2018 -0700" }, "message": "Create scenario tests for load balancers\n\nThis patch implements the tempest plugin for\nfor testing load balancer creation in Octavia.\n\nCo-Authored-By: Jude Cross \u003cjcross@godaddy.com\u003e\nCo-Authored-By: Lingxian Kong \u003canlin.kong@gmail.com\u003e\n\nDepends-On: https://review.openstack.org/557856\nChange-Id: I57064f8e0834efba8859a780394a1c69851cc917\n" } ] }