Gracefully handle paths that are invalid UTF-8 by returning HTTP error
400 instead of an Internal Server Error.
Change-Id: I3b30e4d64e758eefd85f7a70fc645db69991b3d7
Task: 26379
Use openstack-tox-cover template, this runs the cover job
in the check queue only.
Remove jobs and use template instead.
Change-Id: I251086151a23c78f99f39d55b4db36d1db5bc9a0
JsonPayloadSerializer is added in oslo_messaging lib.
This patch suggest to replace current one with oslo_messaging.
Change-Id: I8880ae628b6121e2aee0d132238f44571f3168e3
The current list misses the percentile and all rate based aggregation methods.
Rather than adding them, let's remove the constraint and let Gnocchi and Aodh
validate the data.
Change-Id: I0330c09d72c20d63d08770b52d3071512a418260
* Remove "queue: heat" from check queue, this is not needed.
* Use openstack-lower-constraints-jobs template.
Change-Id: Idde37f299c1cde86b2169fd174539249c23c9962
Some of the project templates brought in via
https://review.openstack.org/#/c/576193/ should have been left in the
project-config repo because they only run on the master branch. This
patch removes those templates.
Change-Id: I727a9ac03781f86845d1af0b2a2ae672665b30db
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
in-place update of failed stacks with old resource references
deleted in last update.
Change-Id: I45fbca77c84744e1778c6f2494674233b9193921
Story: #2003612
Task: 25740
Since we remove a resource's definition after it is deleted, we must also
update a resource's definition after it is updated. Otherwise, a resource
that depended on the now-deleted resource prior to its last in-place update
could remain in the template, leaving the stack inoperable since it is
unable to calculate its own dependencies.
We already update the template in the backup stack when updating resources
in-place, and in the main stack when creating replacement resources. Also
update the main template when resources are updated in-place, not just when
they are replaced.
Change-Id: I97ddc6a970ffd27bfd40bb8f6bec8d1cbf28a815
Story: #2003612
Task: 24946
Several operations (e.g. stack check) are yet to be converted to
convergence-style workflows, and still create locks. While we try to always
remove dead locks, it's possible that if one of these gets left behind we
won't notice, since convergence doesn't actually use stack locks for most
regular operations.
When doing _check_status_complete() on a nested stack resource, we wait for
the operation to release the nested stack's lock before reporting the
resource completed, to ensure that for legacy operations the nested stack
is ready to perform another action on as soon as the resource is complete.
For convergence stacks this is an unnecessary DB call, and it can lead to
resources never completing if a stray lock happens to be left in the
database.
Only check the nested stack's stack lock for operations where we are not
taking a resource lock. This corresponds exactly to legacy-style
operations.
Change-Id: I4eb20ad82cc3e9434da34500fafa3880567d0959
Story: #1727142
Task: 24939
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I33e99114889052d6e610a305c5fb659822d5b0d4
Story: #2002586
Task: #24298
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I4c5227d740cdb0bc9e08ccdce27b0ca73fb4ded3
Story: #2002586
Task: #24298
As we no longer use mox library it is misleading to keep
names starging with mox so let's rename this prefix
to mock_.
Change-Id: Ia376b9dcb7bf964df3c30f6757a6061c1850ee95
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
In the legacy path we reparse a resource definition to refer to a different
StackDefinition when copying a resource definition into the existing
template (as the resource is updated) or into the backup stack's template.
However, the resources 'condition' may reference conditionals that are not
defined in the template it is being copied into (e.g. during a stack update
that creates a new condition), and in this case the destination template
will become unusable.
Since the fact that we care about the resource definition at all indicates
that the condition was enabled, just ignore the condition after reparsing.
This is consistent with what we do for 'if' macros, which is to resolve the
condition part during reparsing.
Change-Id: I59a374435f6275badc8124efbd7b7db2e36e2de5
Story: #2003558
Task: 24847
Removing stack creation limit for admin since admin can view all stacks,
and stacks created by other tenants would have been counted in the limit
check.
Change-Id: Ie2e9251245e7e16309661154e17724e5984c21e6
Story: 2003487
Task: 24756
When a mock hasn't been provided with a long-enough list of side-effects
for the number of times it is called, it raises StopIteration (instead
of something sensible like AssertionError). Prior to Python 3.7, this
exception could bubble up until it just stopped a task. (In Python 3.7
it will eventually be caught and turned into a RuntimeError.)
To ensure that any errors of this sort are not handled silently, and to
enable us to test for them prior to using Python 3.7, catch any
StopIteration errors coming from plugin-provided non-generator functions
and convert them to RuntimeError exceptions.
This reveals many errors in the unit tests, many introduced in the
process of converting from mox to mock, which are also fixed by this
patch.
Change-Id: I5a1eff6b704dff7c17edcbbe58cdbc380ae6abc9
Story: #2003412
Task: 24553
Set_defaults has been added into oslo_middleware. So we use it to
override the configuration defaults.
Change-Id: Ic9c6278e43a66da9f94f556430944fe9b42fb1b7