The neutron functional job wasn't installing neutron, which meant the
sudo config necessary to run the job was not available. It is also
necessary to have devstack install testonly dependencies to ensure that
functional tests can support the same dependencies as the unit tests.
Change-Id: Iee212995f4c27d55466c753ddca6aace4ffcf35e
Partial-bug: #1336172
Also, update the regex in the zuul functions to match
`gate-pecan-tox-scaffolds-33`. This will make the jobs register with gearman so
that zuul can run them.
Change-Id: Ia7d2ff6fd39b7034061f46042e019217857bcbd4
This patch adds the config needed to create and maintain freezer
in Stackforge.
Freezer is an incremental backup and restore automation
tool for file system, MongoDB, MySQL.
LVM snapshot and strong encryption are supported and
data is stored in OpenStack Swift.
See also:
* https://pypi.python.org/pypi/freezer
Change-Id: Ib05a1f11577ba54ccc2c388c15057d6a5ee3199f
msgmerge keeps obsolete translation entries but we should filter them
out. Do the filtering with msgattrib.
Note this is only needed for log files, the other files are handled
correctly since update_catalog has an option for this.
This fixes the issue seen in glance:
https://review.openstack.org/#/c/105069/
Change-Id: I956e4af59d7bbd6e90583bdb9412c9bf85b87019
We were having intermittent failures with the experimental fedora 20
image so we are going to switch to the more tested Ubuntu image.
Change-Id: I3261af31bb07f281ba5acfb083ff46bdaa043e6f
It looks like keystonemiddleware should not have been grouped with
keystone in the review.projects.yaml file (based upon the config
for keystoneclient).
Change-Id: I6c76863a3edb4407e2203413e911d6e1dac1602a
The sqlalchemy migrate special env job for python 26 name does not match
the centos6 assiginment in the zuul openstack functions for node type.
This causes the jobs to end up as not registered with gearman.
Update the regex in the zuul functions to match
gate-sqlalchemy-migrate-26fooblah. This will make the jobs register with
gearman so that zuul can run them.
Fixes-bug: 1347068
Change-Id: I5944889d53656395c98bab9a97cb4e76c793c9fd
As of I7353af4c3f141d4bd617d6fd388d7957e0586ba8 we'll introduce
the ability to have a 2 layer config which includes the messages
that we'll send back to the user on gerrit outside of the
elastic-recheck code base. This makes it easier to make changes
to the UX consistent with what we want to change with the rest
of the config.
Change-Id: I9208123a4cb3be02c272cd8a6eba460f4130a960
Depends-On: I7353af4c3f141d4bd617d6fd388d7957e0586ba8
yum -y in the puppet fails open, which means it doesn't return
non-zero on failure. This means we can make images that don't work.
Until we can figure out why - just install it with a sledgehammer.
Change-Id: I821be58538007cfe93949601216cdf2525c896bb
We would like a new repo on stackforge so we can start tracking comments
and diffs for our blueprints. We are going to attempt to emulate:
https://github.com/openstack/nova-specs workflow to help us organize our
blueprints.
Change-Id: I81aa9ef9924c4bea50f69da0e0641b1beac17264
This reverts commit 466ec42a0023de24518e9e958270637efecdb992.
Since this commit, nodepool has gained a fairer allocator that should
allow better forward progress when contention arises [1]. This should
alleviate the issue of pending devstack jobs not running due to
insufficient fedora nodes under heavy load
[1] https://review.openstack.org/#/c/101110/
Change-Id: I33a3f59dd4601e5cddc3ebd180287d4d8c6fee4c
The gate surely runs into libvirt bugs on a regular basis, but we don't
capture those logs in logstash, so we can't write elastic-recheck
queries against them.
For example, I believe the underlying cause of this issue is libvirt:
https://bugs.launchpad.net/tempest/+bug/1276778/comments/10
Change-Id: Ie2f03b19249967e78319a4016921f91ef0498540
With the 'pip freeze' block at the end of the script, it is not run if
the earlier call to tox to run the doc build fails. Move it up to the
top of the script and run it before the doc build instead.
Change-Id: I7e14ef07599c11babe99f110786a7025d97b1e32
In order to correctly wind-down the 2-node devstack-precise image
add it back at min-ready 0. Once nodes are deleted we can clean
up and remove it.
Change-Id: I4cebaf2b75c67269bed424ead561de43f4165077
