At the moment, deploy_aio.sh is called with sudo which results
in the environment being wiped. This means that all Zuul
environment variables are removed and therefore when zuul-cloner
runs to checkout the branch of kolla-ansible, it will always
fallback to master as ZUUL_BRANCH is unset.
This patch removes the global usage of sudo in the tox.ini file
as there is existing usage of sudo in the bash script itself. This
will mean that we will only escalate privileges when needed rather
for the whole script and the environment variables should be passed
on properly resulting in the matching release of kolla-ansible being
checked out.
Closes-Bug: #1673756
Change-Id: I477a843e696be7136c020be6408afea01967879d
- Remove globals.yml and passwords.yml files.
- The gate was still using these files from the kolla
directory. Modified the gate to prevent using these files
from the kolla directory.
- Modified the deploy_aio.sh file to populate passwords
in passwords.yml using kolla-ansible.
Change-Id: I1ed7849d54cab6d5a9217dced73327ea13f06636
Closes-Bug: #1653035
use different a docker namespace name in case it pull image from
hub.docker.io when deplying in gate
TrivialFix
Change-Id: I643000e5d9e597a254a4f12c0c10186d4eb20429
Signed-off-by: Jeffrey Zhang <zhang.lei.fly@gmail.com>
In the current CI, we have no regitry service. when running pull action,
it will pull image form docker.io where has no such image too.
The right direction is set up a local regitry service, then push and
pull image from there.
TrivialFix
Change-Id: I3ebea5cdb539cb700487a2dbffa894fcce8f8723
* enable the openstack logging debug in the gate
* copy the /etc/kolla files out
* copy the /var/log files out
TrivialFix
Change-Id: I9cf5fa773ec5f41c6ea93325076a64dd24ce22da
rax-iad node has two Ethernets, but others not. Detect the private
Ethernet by using script.
Closes-Bug: #1561563
Change-Id: I7c5d241f2b1a21f97512e52c487d875dd270011b
Use a random virtual_router_id in case there are multi keepalived
instances exist at the same time in the gate.
Closes-Bug: #1568818
Change-Id: Iebb3dec088a21820e641b63bb2a5f40586d1df8c
Avoids errors about missing journalctl on Ubuntu and missing upstart on
redhat bases.
Closes-Bug: 1554724
Change-Id: I80bb55688398df85f9020d5cfe5dda757fc5a0ef
Some gates are failing to properly pull all logs out resuling in an
UNSTABLE status.
This resets all logs to 777 perms to ensure readability by jenkins.
TrivialFix
Change-Id: Ib92c5bfea5fa8bcc6380ad8aa6001b13888717ac
Heka logs almost done. When testing, The collected logs can copy
to the /tmp/logs folder, which will be handle by the gate. This
will be very useful for our gate debug.
TrivialFix
Change-Id: I06ca8ebd13933bfd15cb2fb5e53fc3038b17b8c3
Due to poor planning on our variable names we have a situation where
we have "internal_address" which must be a VIP, but "external_address"
which should be a DNS name. Now with two vips "external_vip_address"
is a new variable.
This corrects that issue by deprecating kolla_internal_address and
replacing it with 4 nicely named variables.
kolla_internal_vip_address
kolla_internal_fqdn
kolla_external_vip_address
kolla_external_fqdn
The default behaviour will remain the same, and the way the variable
inheritance is setup the kolla_internal_address variable can still be
set in globals.yml and propogate out to these 4 new variables like it
normally would, but all reference to kolla_internal_address has been
completely removed.
Change-Id: I4556dcdbf4d91a8d2751981ef9c64bad44a719e5
Partially-Implements: blueprint ssl-kolla
I accidentally merged a patch with +W that does not work on all gates
that infra uses. Specifically it breaks on RAX for unknown reasons.
This is a quick patch to not fully revert, but allow the gate to stay
green while I work out the issue
Change-Id: I02fc66bbc53103f2d71c648d5e2959f10f0130c0
Partially-Implements: blueprint functional-testing-gate
The gate currently doesn't provide any context when ansible fails. This
commit adds a new --verbose option to `kolla-ansible` that is passed to
`ansible-playbook`, and sets the default to -vvv for `kolla-ansible
deploy` in the gate.
TrivialFix
Change-Id: If248a4186b140e1ec0d2e787c27481cec7e81eec
Container maybe exit after deployed. But the print_failure
never runs if the kolla-ansible run success.
This PS checks all the containers status after deploy and
failed the test if the container status is exited
TrivialFix
Change-Id: Ia461b280855eda500e143ee1d6cfd5f215eaf6fe
The existing gate partitioned a disk for use with docker, depending
on the gate it would use the swap disk (RAX) or a spare disk (HP).
However, with the new gates (Bluebox + OVH) there is neither a spare
disk nor a swap disk. This leaves us with one choice: File based loop
device.
This patch creates a file at /swapfile to ensure we have swap. It
creates a file at /docker to ensure we have a loop device for Docker.
Right now the /docker file is 10GB and the /swapfile is 4GB due to
size limitations in the gate across all servers and types. This has
proven to be enough space for all our current tests.
Additionally, reduce the number of threads the gate uses to 4 to
prevent the lockup and hour timeout we have been seeing as more
recently in the gate.
The scripts that setup the gate are moved to the tools directory
rather than the tests directory to match the structure of the other
projects.
Partially-Implements: blueprint functional-testing-gate
Change-Id: I3e370f2382b6df36103d8b2ceda9b21d9b4229d5