baa58e3bf0588942e3ee23f8a6fca5ef8234fe74
15 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
Jenkins
|
baa58e3bf0 | Merge "Remove skips for resize tests from tempest-dsvm-cells-rc" | ||
|
Jenkins
|
f680989dd7 | Merge "cells: skip 5 networking scenario tests that use floating IPs" | ||
|
Matt Riedemann
|
ecf0f67aee |
Remove skips for resize tests from tempest-dsvm-cells-rc
The dependent change disable resize tests in Tempest when running cells and using non-default flavors (which are not in the cells API database). So we can remove the skips from the regex for the cells test runs. Depends-On: I20f46024e45e32c60275703a193a56ae8cfe7eca Change-Id: Ib5d36c4300a84b48faecb2f8181ac0057d4bb4b8 Related-Bug: #1513925 |
||
|
Sean Dague
|
876679c08f |
cells is a sad panda about scheduler hints
The new test_schedule_to_all_nodes test fails in some epic ways in cells. Not really worth debugging, this is a new test and had just exposed another cells / devstack issue. Just skip the test. Change-Id: Icc71e36f4ecb015dff9e806caacd31262f7e17f7 |
||
|
Matt Riedemann
|
8adc0e30a7 |
cells: skip 5 networking scenario tests that use floating IPs
These scenario tests run with neutron and rely on assigning floating IPs which cells v1 doesn't support, so skip them. Longer term I think we'll have a feature toggle in Tempest to allow disabling these tests via config but this is quicker and easier for now to get a cells v1 + neutron job in the experimental queue. Change-Id: Ieb3b117449f56810f1a41fcf43e737ae919b8945 |
||
|
Sean Dague
|
387e2b4fbb |
clean up regex in tempest-dsvm-cells-rc
The current regex contains a lot of slightly off regex definitions. Most of them don't hurt, and do still match the correct way, but they make people believe that things like the * at the end of matches is important (which it is not). This cleans this up, plus adds a few comments to help people going forward. Change-Id: Ica7fc32fd5a756214db987b95d2305bc74cfb6f1 |
||
|
Sean Dague
|
02de17c72a |
skip lock_unlock_server test for cells
The cells architecture of doing db replay makes this call fundamentally racey for cells. The contract is that if you request an action on a server and it is locked, you get a 409 at the API, and are done. If you get a 2xx, the resource is not locked, and life is good. Except in cells, the API db will be updated, and the API will return all is well. Except the db replay hasn't happened for the cell, so the additional check in the nova compute for locked blows up. The fix probably involves the nova-compute check doing a timed retry under cells because of replication lags. Change-Id: Ic18407b8372c286d8e258860f3e2bf76eceef2aa Related-Bug: #1466696 |
||
|
Sylvain Bauza
|
fa203c3165 |
Exclude all BDM checks for cells
Since there are some race conditions with the EBS image checking test, it's better to remove the entire Tempest class tests just until we figure out what's wrong with the boot from volume stuff Change-Id: Ice6a718b6d7b27505696a3c55fc02d44d4b187a7 Related-Bug: #1489581 |
||
|
John Garbutt
|
790d6b31da |
Add tempest-dsvm-lxc-rc
This is the test exclusion list that will be used by the new *tempest-dvsm-lxc job. Co-Authored-By: Matt Riedemann <mriedem@us.ibm.com> Change-Id: Ic7ad85958ef0ef6576a868b9c4485868523c8e52 |
||
|
Jenkins
|
411769be8f | Merge "Creating instance fail when inject ssh key in cells mode" | ||
|
Chung Chih, Hung
|
371be3f4a9 |
Creating instance fail when inject ssh key in cells mode
The conductor service of compute host will try to find ssh key in child cells when creating instance. But the ssh key was only stored at parent api cells. Therefore the conductor service will throw ssh key not found exception. There are three solutions: 1. add keypair_type into the instance object, along side keypair_name, etc 2. Sync ssh keypair to every child cell database 3. consider sending a message to the parent cell to fetch the keypair This commit prefer to use third solution. Because of the data ssh keypair should be global. And cells v2 split key_pairs table into global API tables. Change-Id: I156a1c3cf3e31f34cea5e240b14a9575e9e45239 Closes-Bug: #1443816 |
||
|
Jenkins
|
f1f799183f | Merge "Remove the blacklisted nova-cells shelve tests" | ||
|
Sylvain Bauza
|
f45ace1e64 |
Fix Cells gate test by modifying the regressions regex
Ie4ffd458456d03b0b817b01bbed391f359240db2 changed some TestCases names with the consequence that those tests were becoming not excluded and consequently the cells job was failing. Change-Id: I81ae2918355a02c4e20470a924538d2c7fbafcf6 Closes-Bug: #1492255 |
||
|
Chuck Carmack
|
4185846831 |
Remove the blacklisted nova-cells shelve tests
nova-cells does not support the shelve feature. Since the nova-cells shelve tests are now disabled using the tempest feature config options, we can remove the shelve tests from the blacklist. Change-Id: Iad51bfcff49b7eabc46101bd7f956adfa5958ced Closes-bug: 1491152 Depends-On: Ibf1f9aaa63e5f17b7d8774b511940ba8421e0887 |
||
|
Matt Riedemann
|
78ed3ae253 |
cells: add devstack/tempest-dsvm-cells-rc for gating
We need to whittle down the large regex of excluded tests for the tempest-dsvm-cells job but we also need to be able to test changes to the regex, like removing entries that we think are now working. This change moves the regex from project-config in the tempest-dsvm-cells job definition to nova so that nova can control and test the changes on it's own, since project-config is not currently able to self-test job changes. project-config change: I8cbc36266eadaf0dbef20e3e83f4874bcfc9ab3a Change-Id: I2365619de4ba7b43a049771bac90d2deebaa3e9c |