Tree:
14a3b1318c
master
stable/pike
stable/queens
stable/rocky
stable/stein
stable/train
stable/ussuri
stable/victoria
stable/wallaby
stable/xena
stable/yoga
0.9.0
12.0.0
12.0.0.0b1
12.0.0.0b2
12.0.0.0b3
12.0.0.0rc1
12.0.0.0rc2
12.0.0.0rc3
12.0.0a0
12.0.1
12.0.2
12.0.3
12.0.4
12.0.5
12.0.6
13.0.0
13.0.0.0b1
13.0.0.0b2
13.0.0.0b3
13.0.0.0rc1
13.0.0.0rc2
13.0.0.0rc3
13.1.0
13.1.1
13.1.2
13.1.3
13.1.4
14.0.0
14.0.0.0b1
14.0.0.0b2
14.0.0.0b3
14.0.0.0rc1
14.0.0.0rc2
14.0.1
14.0.10
14.0.2
14.0.3
14.0.4
14.0.5
14.0.6
14.0.7
14.0.8
14.0.9
14.1.0
15.0.0
15.0.0.0b1
15.0.0.0b2
15.0.0.0b3
15.0.0.0rc1
15.0.0.0rc2
15.0.1
15.0.2
15.0.3
15.0.4
15.0.5
15.0.6
15.0.7
15.0.8
15.1.0
15.1.1
15.1.2
15.1.3
15.1.4
15.1.5
16.0.0
16.0.0.0b1
16.0.0.0b2
16.0.0.0b3
16.0.0.0rc1
16.0.0.0rc2
16.0.1
16.0.2
16.0.3
16.0.4
16.1.0
16.1.1
16.1.2
16.1.3
16.1.4
16.1.5
16.1.6
16.1.7
16.1.8
17.0.0
17.0.0.0b1
17.0.0.0b2
17.0.0.0b3
17.0.0.0rc1
17.0.0.0rc2
17.0.0.0rc3
17.0.1
17.0.10
17.0.11
17.0.12
17.0.13
17.0.2
17.0.3
17.0.4
17.0.5
17.0.6
17.0.7
17.0.8
17.0.9
18.0.0
18.0.0.0b1
18.0.0.0b2
18.0.0.0b3
18.0.0.0rc1
18.0.0.0rc2
18.0.0.0rc3
18.0.1
18.0.2
18.0.3
18.1.0
18.2.0
18.2.1
18.2.2
18.2.3
18.3.0
19.0.0
19.0.0.0rc1
19.0.0.0rc2
19.0.1
19.0.2
19.0.3
19.1.0
19.2.0
19.3.0
19.3.1
19.3.2
20.0.0
20.0.0.0rc1
20.0.0.0rc2
20.0.1
20.1.0
20.1.1
20.2.0
20.3.0
20.4.0
20.4.1
20.5.0
20.6.0
20.6.1
2010.1
2011.1
2011.1rc1
2011.2
2011.2gamma1
2011.2rc1
2011.3
2011.3.1
2012.1
2012.1.1
2012.1.2
2012.1.3
2012.2
2012.2.1
2012.2.2
2012.2.3
2012.2.4
2013.1
2013.1.1
2013.1.2
2013.1.3
2013.1.4
2013.1.5
2013.1.g3
2013.1.rc1
2013.1.rc2
2013.2
2013.2.1
2013.2.2
2013.2.3
2013.2.4
2013.2.b1
2013.2.b2
2013.2.b3
2013.2.rc1
2013.2.rc2
2014.1
2014.1.1
2014.1.2
2014.1.3
2014.1.4
2014.1.5
2014.1.b1
2014.1.b2
2014.1.b3
2014.1.rc1
2014.1.rc2
2014.2
2014.2.1
2014.2.2
2014.2.3
2014.2.4
2014.2.b1
2014.2.b2
2014.2.b3
2014.2.rc1
2014.2.rc2
2015.1.0
2015.1.0b1
2015.1.0b2
2015.1.0b3
2015.1.0rc1
2015.1.0rc2
2015.1.0rc3
2015.1.1
2015.1.2
2015.1.3
2015.1.4
21.0.0
21.0.0.0rc1
21.0.0.0rc2
21.1.0
21.1.1
21.1.2
21.2.0
21.2.1
21.2.2
21.2.3
21.2.4
22.0.0
22.0.0.0rc1
22.0.1
22.1.0
22.2.0
22.2.1
22.2.2
22.3.0
22.4.0
23.0.0
23.0.0.0rc1
23.0.0.0rc2
23.0.1
23.0.2
23.1.0
23.2.0
24.0.0
24.0.0.0rc1
24.0.0.0rc2
24.1.0
25.0.0
25.0.0.0rc1
diablo-1
diablo-2
diablo-3
diablo-4
diablo-eol
essex-1
essex-2
essex-3
essex-4
essex-eol
essex-rc1
essex-rc2
essex-rc3
essex-rc4
folsom-1
folsom-2
folsom-3
folsom-eol
folsom-rc1
folsom-rc2
folsom-rc3
grizzly-1
grizzly-2
grizzly-eol
havana-eol
icehouse-eol
juno-eol
kilo-eol
liberty-eol
mitaka-eol
newton-eol
ocata-em
ocata-eol
pike-em
queens-em
rocky-em
stein-em
train-em
ussuri-em
victoria-em
${ noResults }
5 Commits (14a3b1318cf84983e1c029ffa1d3a7b2d0223779)
Author | SHA1 | Message | Date |
---|---|---|---|
|
14a3b1318c |
Skip test_parallel_evacuate_with_server_group until fixed
This test has a high failure rate so let's skip it until the bug is fixed: http://status.openstack.org/elastic-recheck/#1763181 Change-Id: Idcd2e7118c8d985d6d2cc4b12c08388406229bbf Related-Bug: #1763181 |
4 years ago |
|
c333e7e12e |
Raise error on timeout in wait_for_versioned_notifications
fake_notifier.wait_for_versioned_notifications previously returned None if it timed out. This is counter-intuitive, and several callers were failing to check its return. Every one of these represents a race as it means we can continue past a barrier without its condition having been met. This change makes it default to safe by raising an exception if it times out. Note that it's possible this may subsequently result in new non-deterministic errors in functional. I would consider this a feature, as these were previously hidden. They should be addressed individually. This change highlights several deterministically incorrect uses of wait_for_versioned_notifications which were previously always silently timing out. These are all fixed. We also increase the default timeout from 1 to 10 seconds as we seem to hit the 1 second timeout in practise, e.g.: http://logs.openstack.org/46/578846/14/check/nova-tox-functional/8a444c1/job-output.txt.gz Change-Id: I017d1a31139c9300642dd706eadc265f7c954ca8 |
4 years ago |
|
5133a543b9 |
Remove unused LOG variables
TrivialFix Change-Id: I84f80aa75fb455039e5b56ae4d49a5f77db9097a |
4 years ago |
|
edeeaf9102 |
Add late server group policy check to rebuild
The affinity and anti-affinity server group policy is enforced by the scheduler but two parallel scheduling could cause that such policy is violated. During instance boot a late policy check was performed in the compute manager to prevent this. This check was missing in case of rebuild. Therefore two parallel evacuate command could cause that the server group policy is violated. This patch introduces the late policy check to rebuild to prevent such situation. When the violation is detected during boot a re-scheduling happens. However the rebuild action does not have the re-scheduling implementation so in this case the rebuild will fail and the evacuation needs to be retried by the user. Still this is better than allowing a parallel evacuation to break the server group affinity policy. To make the late policy check possible in the compute/manager the rebuild_instance compute RPC call was extended with a request_spec parameter. Co-Authored-By: Richard Zsarnoczai <richard.zsarnoczai@ericsson.com> Change-Id: I752617066bb2167b49239ab9d17b0c89754a3e12 Closes-Bug: #1735407 |
4 years ago |
|
33d87707d8 |
Add regression test for bug 1735407
Parallel evacuation can violate server group policy. This patch adds functional test to recreate the bug. The _wait_for_migration_status helper needed to be moved upper in the test calls hierarchy so it can be reused for this test too. Change-Id: I5bc50f9c0913a5b02c42f4ab201e9bf097395b54 Related-Bug: #1735407 |
4 years ago |