new cleanup-host script removes kolla-build.conf
in /etc/kolla directory which contains the build
configuration for building images.
This should be preserved.
Change-Id: I20fbf3f8a2400a5e048ba55beb0c8e1ec849d8a3
Related-Bug:#1561055
In the gate, it is possible for /etc/hostname to not have a valid
SELinux security conext. So, reset them to default before we update
the hostname to avoid:
TASK: [Assign hostname]
failed: [node1] => {"failed": true}
msg: Command failed rc=1, out=, err=Could not set property: Access
denied
Closes-Bug: #1568047
Change-Id: Ie30c8437b310d1ea5bc75307375c255131dfe934
Needed-By: I2ff5fbb315832b8cf07c93d0dd0cdaacd958631e
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
Kolla deployment creates /etc/kolla folder on a target host
with multiple configuration files. In some scenarios,
the presence of these files prevent successful deployment
of certain services especially when their configuration parameters
have been changed on the deployment host.
Change-Id: Iefd544b50fc90b7f00d6e137bc14ab4807ef7c0f
Closes-Bug: #1561055
The nova team is removing the default flavors from a standard
deployment. This is great for operators, who have to delete
the defaults anyways. This patch adds the original default
flavors back during init-runonce so kolla users can be ready
to launch instances.
Closes-Bug: #1567964
Change-Id: I17daec98997a6e412a99f34d3f8a4324460d8c60
After run cleanup-containers script, was necessary to
clear references to the ceph in fstab file manually
Change-Id: I264e6644d5d569a9b56115ea31b15589b093c3f9
Closes-Bug: #1562991
A recent change related to sudo securepath broke how sudo -E
works. Now the PATH is reset by sudo as set by tox. As a result
we can no longer rely on sudo -E anywhere in our gating system
relating to path inheritence from the parent shell.
This patch uses a shell operation in the setup_nodes.yml code
to chmod the docker socket to 666 so docker containers can build
properly. Now docker operations don't return a permission denied
and we no longer require the sudo -E operation in any of our tox
scripts. This isn't a security vulnerability because our gate
scripts are only meant to be run in OpenStack infrastructure.
To make this more clear I recommend moving these shell scripts to
tests/gate.
Change-Id: I5b3d6e280e3c12a25defedb14b5589ba642043fa
Closes-Bug: #1562383
Avoids errors about missing journalctl on Ubuntu and missing upstart on
redhat bases.
Closes-Bug: 1554724
Change-Id: I80bb55688398df85f9020d5cfe5dda757fc5a0ef
As with all tools, this is a first pass at the generation. Perhaps we
even want to move this into kolla/kolla/cmd and be generated with tox
itself in the future.
This tool, when run, will only populate empty fields that have no
values meaning that it is safe to run repeatedly on the same file.
Of note, there is no way to preserve comments in the file after it has
been processed by the yaml parser in python. Comments and sections
will remain in the passwords.yml template for additional documentation
if the user wishes to populate the file themselves.
Use SystemRandom and clean up the docs a bit to not use pronouns.
Co-Authored-By: Steven Dake <stdake@cisco.com>
Closes-Bug: #1559266
Change-Id: I2932d592df8871f1b7811059206d0b4d0553a687
This also fixes this version check utility since it was utterly broken
before. While it did run to completion, it never properly returned any
versions that needed updating.
TrivialFix
Change-Id: If5d77f20fd8fc97679d58bc9019115157c5f5967
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
This playbook only matters for multinode since AIO can recover from
power outage without additional configuration.
DocImpact
Implements: blueprint mariadb-lights-out
Change-Id: I903c3bcd069af39814bcabcef37684b1f043391f
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
This change is a "futureproofing" thing. It has already been discussed
that libvirt should not be a child of nova and should be removed out
to the base docker directory (just like openvswitch isn't a child of
neutron). That is not going to happen this cycle but when it does we
can't change the name of the volume. This updates the volumes to the
proper name of libvirtd. This is in contrast with the libvirtlogd
volume that will be needed in newton due to libvirt 1.3
Of note, the container can remain named nova_libvirt since we can
change that on the fly later without breaking instances.
This wont break liberty as named_volumes are not backported yet.
TrivialFix
Change-Id: I16cf9e1b1dbba9b5a9f5cc883494580e276d4f72
The rabbitmq-server package is upgraded to 3.5.7 in cloud-archive
so we update centos to match
The xen-utils package now needs an explict version, xen-utils-4.6 is
what is provided by cloud-archive mitaka
Libvirt 1.3 is in the ubuntu cloud-archive. This has a new daemon for
logging that needs further implementation in newton. For now, it has
been disabled within the qemu.conf
Co-Authored-By: Jeffrey Zhang <jeffrey.zhang@99cloud.net>
TrivialFix
Change-Id: I84217824817c484b6800a64cbd7767b127a3098e
Add cron image and playbook for logrotate.
The "common" Ansible playbook includes configuration files for
logrotate. At this point the operator cannot customize/override the
logrotate configuration.
Closes-Bug: #1553244
Change-Id: Ic9fdda9a273c9ccd90502f0acc7614d2c7157dca
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
As we will be switching to pinning versions in Kolla this tool will
help remove the 'manual' part of that equation by looking up the
versions we want.
The idea would be to eventually turn this into an autoproposal bot so
we only ever need to approve changes.
More work can be done here like automatically updating the
kolla-build.conf
Co-Authored-By: Martin André <m.andre@redhat.com>
Partially-Implements: blueprint upgrade-kolla
Change-Id: I052159850b2579ca6db79be71672be382be8a3a3
