This reverts commit 4e8a3ca6b2041c170f4073499ee0315616396af2.
This is handled generically with this change and its dependency:
https://review.openstack.org/#/c/606853/
Change-Id: Ic79cc07a2d11772c1892b2db8c4c02cc7be4081c
This was correct for the RDO installation guide.
This reverts commit b90278b503aff2ad8148af38525beb90ffb117d8.
Change-Id: I5107e712a903f334f1a3a996b9140e9e2fe0807a
With moving away from required milestone releases, the version numbers
calculated by PBR on the master branch will not work for those testing
upgrades from the last stable release. More details can be found in the
mailing list post here:
http://lists.openstack.org/pipermail/openstack-dev/2018-October/135706.html
This is an empty commit that will cause PBR to increment its calculated
version to get around this.
PBR will see the following which will cause it to increment the version:
Sem-Ver: feature
Please merge this patch as soon as possible to support those testing
upgrades.
Change-Id: Ifbba36f4974efcf891c7f5938acfeef75bb05dd2
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Quotes around {posargs} cause the entire string to be combined into one
arg that gets passed to stestr. This prevents passing multiple args
(e.g. '--concurrency=16 some-regex')
Change-Id: Iccbd680731592abab4980a51aa97c60d6ef95005
We use the notify.signal() call to notify the main thread that the stack
status has moved to IN_PROGRESS so that it can wait before returning
control to the user. Therefore it is expected that if an operation
eventually fails (or succeeds), signal() will have been called a long
time previously. The only reason it is there is to guard against
failures before the resource attains the IN_PROGRESS state, where the
persistence of the state has been deferred to coincide with the lock
release.
Story #2003988
Task: 26931
Change-Id: Ie0519ee78607f71855c2c0ace2cb4ff52c5809b6
This adds a limit to the number of resources that ResourceChain creates
in parallel. It reduces memory usage drastically when ResourceChain
contains lots of resources. We use the number of active services, which
seems to give a reasonable balance between performance and memory
consumption.
Story: #2003975
Task: #26917
Change-Id: Id20fb89813b32927298b3a7c0abe23da710b04d1
In 866864f7e5973053edcd9de59caab05790729964 we changed to use
noop drivers, we don't seem to set them correctly.
Depends-On: https://review.openstack.org/605000
Change-Id: I7ba69fc047334c9c3d2fffe41e586650f9fb372b
In order to get openstack/placement installed as part of the
heat grenade jobs, we have to list it as a required project.
Needed by https://review.openstack.org/604454/
Change-Id: I58fae5f56fdbcb4fc084689bde95f1a2c4bfad0f
It's possible that the volume is already attached to another
server, which can happen by marking a VolumeAttachment resource
unhealthy after removing the volume from the server.
Change-Id: Ia77e0462bf732224b491591d22584cbcfa779956
Story: #2003850
Task: 26643
When a heat-engine thread activity completes, it calls release on
its stack_lock object in the database. If that release action fails
due to an inability to update the database, that engine process is no
longer usable. This code catches that failure, logs it, and terminates
that engine process so that a new one can be started. New heat engines
will automatically purge stale stack_locks from the database.
Also, make sure that if the thread exit does not teardown the process
after 5 seconds, the non blockable os level exit call will be invoked.
This bug is very timing specific. The DB error needs to exist when the
stack_lock release fails
Change-Id: I7663b2270bf325cd8e3dd194f2994227fd6f5e8a
Story: 2003439
Task: 24635
keystone endpoint region can be different from other services.
Let's use the one from keystone middleware authtoken config,
if available, when creating keystone client.
Change-Id: I190abd946db1cf8712ef669cf72a1134dfcf9376
Story: #2003806
Task: 26549
Continue to test Heat's interaction with the Octavia API without relying on
Octavia's interaction with Nova, Neutron &c. which is known to be unstable.
Change-Id: I8765aceee09ada3086abc704b7f73ce240e21847
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>