| Age | Commit message (Collapse) | Author | Files | Lines |
|
Currently CentOS gates use btrfs storage driver and
create /docker device backing btrfs.
This patch is to sync the gate run with Ubuntu.
(post-Trusty) does not use btrfs, only overlay2.
Change-Id: Ic5caa8cf0271b21f71f03fd33c35b3c7bc93ccf4
|
|
Currently CentOS binary jobs are often failing due to running out of
storage while building images.
See
http://logs.openstack.org/87/612887/8/check/kolla-build-centos-binary/b467920/logs/build/000_FAILED_heat-all.txt.gz
for an example, and
http://logs.openstack.org/87/612887/8/check/kolla-build-centos-binary/b467920/logs/df.txt.gz
for the corresponding df output that shows the /var/lib/docker loopback
mount at 97%.
Change-Id: I2f3d04452c517f8643b124550148cc9d8320b937
|
|
This is zuulv3 migration patch. This patch only implement build jobs.
Deploy jobs will be pushed in another one.
Partial-Bug: #1720601
Change-Id: Ib9157ed132820d752ef1dbd7a53353ebd68b1934
|
|
TrivialFix
Change-Id: I73d208d2a52c018ad6027f811c6b3a2eee802015
|
|
Sometimes gates fails due lack of space,
post merge jobs gates fails always for oraclelinux
binary, not being able create a tarball registry.
This change mounts a second disk in opt and moves
registry data to opt.
Disk format commands are excepts from devstack-gate:
https://github.com/openstack-infra/devstack-gate/blob/dc49f9e6eb18e42c6b175e4e146fa8f3b7633279/functions.sh#L306
Closes-Bug: #1713652
Change-Id: I883e51042841709eb9ab348cfdce9fecbd4fb890
|
|
Change-Id: I1cb6189cec2704edfc461538ef593d38e81ca343
|
|
There were a few issues blocking Kolla from going up to the
latest version of Docker which is 1.13. Most of these issues
seem to have been addressed by 1.13.1.
This patch updates the version installed by Kolla to 1.13.1
for the testing infrastructure to prevent the following
bug which is causing gate failures:
https://github.com/docker/docker/issues/28336
Change-Id: I0d3569b589ee792c9aa6eaa7c539219fcc784271
|
|
* Push images all the time
* Pin docker-engine version
Change-Id: Ie778f719655c1136e563ede9e494b37817e247fa
|
|
Part of plan to have registry-like behavior in deploy gates. First part
is to run docker registry locally. Next one will be pushing built images
to it, tar.gz whole registry (separate per distro and type) and use
publisher jobs to upload whole registry to tarballs.o.o
Change-Id: I81f154fe6ef58ef93815f42496aef382d32f6774
|
|
TrivialFix
Change-Id: Iaa8ff2592d89a91081383e1f9c23c860bb73bba5
|
|
Docker engine is updated to 1.12. The docker.service in the rpm is
change. Use the /etc/systemd/system/docker.service.d/kolla.conf file to
overwrite the default parameters
TrivialFix
Change-Id: Ice56808f4a1ce1ee57bf5e48c779d033ea6c759c
|
|
Previously, when either setup_{RedHat,Debian}.sh was ran
multiple times a mess was created due to multiple loop
devices being setup.
This change now looks to see if '/docker' or '/swapfile'
already exist, and not re-create them if they do.
*However*, /var/lib/docker (/docker) is still wiped - but it
means that the script can run and bring the system into a
constant vanilla state.
Change-Id: I169662fa04c2bf644672ca75c3ee579795943727
Closes-Bug: #1586563
Signed-off-by: Dave Walker (Daviey) <email@daviey.com>
|
|
this is a wordround fix for the rabbitmq failed when deploy on CentOS in
the CI gate. the ideal fix should set the hostname in setup_gate.sh
script. But it do not work as expect with unknown reason
Partial-Bug: #1581301
Change-Id: Ia692794aadf11d3ebe75e4e2bf6b42d9a5f3996f
|
|
Change-Id: Ie9fc941bb48edf86b00fc1f2dba0b83b675a5a1c
Partial-Bug:#1569417
|
|
Currently the binary build for the oraclelinux base is just exceeding
the 10GB limit we have set here. Centos is at just under 9GB so will not
be long before it reaches this limit also.
According to infra -
(http://docs.openstack.org/infra/system-config/contribute-cloud.html)
gate VMs should have a 80GB disk, so 20GB for the docker partition does
not seem excessive here.
TrivialFix
Change-Id: I4d7fb240ea90e1e58f8f8046dd7acd0b9502c20d
|
|
Docker 1.10 has broken the gate and this patch will correct that
breakage.
The issue comes with rsyslog. Due to a commit in Docker 1.10 [1] we
must change the way we get the log socket for rsyslog. The /dev/
folder will no longer populate as we used it. So instead we simply
make a new socket in a path we control and share that to the correct
location in the containers.
Additionally, adjust the gate for new Docker daemon.
[1] https://github.com/docker/docker/pull/16639
Partially-Implements: blueprint kolla-upgrade
Change-Id: I881a2ecdf6d7b35991e1d38a3f3e60d022d6577f
|
|
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
|