Rebase to resolve tempest run error #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CINDER_SECURE_DELETE was deprecated in devstack in liberty with dfcc3871c022516330b6afb6c74751ac42a87480. Start using CINDER_VOLUME_CLEAR (default to 'none' to avoid the same bug that CINDER_SECURE_DELETE is used for). Add a TODO about removing DEVSTACK_CINDER_SECURE_DELETE once kilo-eol happens in devstack. Change-Id: I131c1aee665d6bd4e38dcfd0aec1b4796adc64c5
Fix some misspellings Change-Id: Id9ac593a585f8d348667e6f208b8327d72502d17
devstack can configure a TLS proxy for a number of services if the tls-proxy service is enabled. Make this service available to the gate. Change-Id: I654f06c34a60e56ff98b9b6720d0f9a3fe5d240b
The left bracket '[' was incorrectly placed. And '-f' was trying to be executed instead of the test executable '[' Change-Id: Ib947fa6aab651e427e44c8edc3552a02f3b505a4
Change #openstack-dev to #openstack-qa in README.rst Use #openstack-qa as that is the channel that patch submission notices get broadcast on. Change-Id: I8ea331bbb325182e465f68f91930886822ba3c9c
The commit 7ffa1d58ce9fd9e32cdab142a1f12feae38c3097 added support to configure nodes with ipmitool drivers in DevStack ironic to run with virtual machines. The main goal of that patch was to allow us to test the production ipmitool drivers in the gate replacing the *_ssh testing drivers in the future. Later a patch to project-config 2e577710e975983b594f6df59b504b4cae85e594 added two new jobs to the ironic gate: pxe_ipmitool and agent_ipmitool. This patch contains the final pieces to enable ipmitool drivers to run on gate. Change-Id: I2adff0d7195d3f53e19b600b2d91163a8271bf2c Related-Bug: #1544642
We switched from GRE to VXLAN in the implementation as of I951e7e1bd98eeaf347e85296c12e027e225c2c97 so the diagrams should match accordingly. Change-Id: I0b0cef3a7217530573e694de54bf6dc68e295856
Don't always assume our MTU will always be 1500 when calculating the MTUs of overlays running inside our test nodes. Instead determine our smallest interface MTU, subtract 50 from that for vxlan overhead (and GRE too since GRE has less overhead than vxlan), and use this new number on the overlay networks. Change-Id: If5facee99f03c0ec4773241f872477b922a6674e
Previously we had wrongly assumed that python yaml package will be available in the images and the run-tests.sh script ran a set of things which included a script that used the pyyaml package. With the recent bindep changes, this assumption broke and the gate-devstack-gate-unittests failed. So we need to install the pyyaml package and then run the tests in this venv for run-tests.sh to work. Change-Id: I541c8add8041348a259b3b789d24cf24ba122ce0
If the ironic VM node console logs exist in the /opt/stack/old/ directory then archive those logs as part of cleanup_host(). Change-Id: I5349f33c94654534825a7b0a88eb2e5bc8092394
Makes it easier for folks to go look in one spot for deprecation warnings spit out in various process(es). This will also help us warn folks to go fix deprecated stuff before they become a problem. Change-Id: I757821bd6f19a168888df92d416d7af16f41637b
Change-Id: Ie4f86c812d4de5cd5987833f377efde4921875b3 Signed-off-by: Doug Hellmann <[email protected]>
Oops! missed the location for the Apache based logs (horizon and keystone). Change-Id: I7d20e95b3ed9f37bfe04865e8809795964a49455
It is not possible to use a swapfile generated by fallocate on a xfs filesystem which is shipped by default on CentOS >7. So since [1], we effectively ran jobs on CentOS VMs without any swap. Use dd as a way of creating the swapfile that works on both Ubuntu and CentOS with a slight performance hit and ensure it's mounted properly so we don't have a silent failure. Also manage a new specific case, Vexxhost VMs ship with 2GB of swap which is not in line with the expectation that all VMs should have 8GB. If there is less than 8GB of swap (or zero), we will make up for the difference. [1]: https://review.openstack.org/#/c/278557/ Change-Id: Iaf4de66475d747f62bd49dfe7318131cbeb03be8
The script to populate reproduce.sh is failing when populating multi-line env vars. That is the case of the enable_plugin lines, when more than one plugin is enabled. Add this workaround to properly populate all needed settings. Also add a test to ensure that reproduce method is working as expected. Change-Id: I5287098a47162321efadbde7d069fa2a4e7eabf7
Fix so that ~/workspace-cache is no longer deleted. Makes instructions in README work again. Change-Id: I71668132820137f50b32494bc78d58a80867be92
This documents the prerequsites and requirements for reproducing devstack-gate in Ubuntu Trusty. Known issue: Doesn't document this for CentOS/Fedora. Change-Id: I6c483d6af7afda4d4ebb914dc7bd6ee862ad874f
As of now, there is no way to address 2 different set of configuration for the primary node and the subnodes when using the multinode tests. Hence, this patchset adds a new environment variable called DEVSTACK_SUBNODE_CONFIG that appends its content into the local.conf file of the subnodes (only). Besides, the existing DEVSTACK_LOCAL_CONFIG variable is still used to set up the primary node. Change-Id: I1603b747b2cf4767cd3ed71fe4d56ae54920d19e
This makes grenade work with stable mitaka, both upgrading to it, and upgrading from it in master. Depends-On: Ic9fc5cde67691ce03b3d612d86da7207608e20b1 grenade fixes for OS_PROJECT_NAME Change-Id: I73d2f7f83f700e430d231235e6d2277100036cd5
When DEVSTACK_GATE_VIRT_DRIVER has been set to ironic, in function setup_localrc, VIRT_DRIVER=ironic will be set to local.conf twice. This fix remove the second write. Change-Id: I6c0e7649366e3567b9342e4f83489dbae0229c2b Closes-Bug: 1561279
Bad copy and paste, this should have been liberty. Change-Id: I42e0971bbbb2e14bf75f5399811122c64594661e
A recent bug was due to the locale configuration of our nodes. While it is unlikely we'll have that issue again it's still worth logging the locale for future analysis. Change-Id: I25c945b2a1e13fb1012c653f56ecd5c14e320677 Related-Bug: 1560808
'ironic-multitenant-network' job build/delete 2 instances and can't be completed in current TEMPEST_OS_TEST_TIMEOUT 900 sec. This patch allow to pass TEMPEST_OS_TEST_TIMEOUT from the gate job via DEVSTACK_GATE_OS_TEST_TIMEOUT variable to Ironic jobs. If DEVSTACK_GATE_OS_TEST_TIMEOUT is not set, timeout will be configured to current value 900 sec. Change-Id: I3f0833a4d3371846cb67eeb1cfe0946abc3d3772
If the Jenkins Job definition adds items to the PROJECTS variable that are not included as we build up PROJECTS reproduce.sh will ultimately fail. The fix saves the PROJECTS as it is passed into devstack-gate-wrap and includes that in reproduce.sh. Change-Id: Iea45f53b8c26985cb0da9720a631fcf8725522cf Closes-Bug: bug/1544827
We should transition to the DevStack fwaas plugin, similar to what was done in c59dfac Change-Id: Iadcee07e873fcb4f099ebccc2e33780e74438140 Related-Change: If6c6e032689392fecc8c24517666128c8c103a7b Related-Change: Ic60cd1fa90c19dfac00be583e2ddc5633dbb68a3
Some test jobs use pre-provisioned credentials. It can be useful to have the credetials file for troubleshooting purposes, so copying it to the logs folder when available. Change-Id: I9fcb3497387fb32f3e515cda44a1a105921a04c2
OS_TEST_TIMEOUT may be passed via DEVSTACK_GATE_OS_TEST_TIMEOUT project-config variable. Change-Id: Id81e9060fb0b7800cba1345ea3c8f28b1a691759
With the new zuul rsync copy, the apache/ directory disappeared from view as its permissions are copied verbatim into the log directory and it's not world readable. Correct permissions on $BASE/logs so that everything is readable. Change-Id: Ia034c5176937f579e0f19504c6f0ef9c118869b8
Cinder team is planning to start multinode testing in Newton cycle. We want to be able to test volume migration/retype and partial grenade. This commit enables c-vol and c-bak on the subnode in regular multinode setups (this should work as I4d2960d92f388ac689dfa6b436dc8bfc1e129fbf is merged now). Also a new features.yaml elements are introduced that would disable c-vol and c-bak on primary node. This will be required for multinode grenade jobs that will test compatibility of master c-api and c-sch with stable c-vol and c-bak. Co-Authored-By: Karthik Prabhu Vinod <[email protected]> Change-Id: I4532bdcfa845cf0a405f68371c61559b0a70f9c1
The network_device_mtu option will be removed from Neutron in Newton. The global_physnet_mtu option was introduced in Mitaka. Before Mitaka, Neutron did not have any multinode jobs that would require setting the infrastructure MTU for inter-node connectivity. Change-Id: I337b284076a794027fbd63796119d56bd1923cf2 Related-Bug: #1603493
Previously we were only setting the mtu on br-ex if not running grenade. But now neutron runs multinode grenade tests so need to have br-ex's mtu set appropriately for grenade and devstack both. This is done by using PUBLIC_DEVICE_MTU devstack variable that will guarantee the bridge is set appropriately in both devstack and grenade cases. Change-Id: I9bcc47303a6ce1f0b3125ad374adcc2e7ca654ac Depends-On: I38a80bac18673a30842a7b997d0669fed5aff976 Related-Bug: #1603268
arp can resolve the gateway address to something unhelpful like "gateway" which fails the grep. Avoid this. Change-Id: I236b7080774fef8700d0ec056d9703eb98f90204
By default ntp-wait waits 6 sec * 1000 tries = 100 mins It breaks long jobs like in TripleO projects because of waiting for 1 hour 40 minutes. If ntp wasn't synced during first 10 min it most likely won't be synced at all, so no reason to wait so long time and break jobs that date is not critical for them Change-Id: Iae28a03829a255f0990934685d8c2e563a7a8492 Partial-Bug: 1608226
We'd like to change the default for this in our local devstack plugin, but until devstack-gate sets the desired value in all cases we can't. Change-Id: I25c2ece32b7e8b601fe5ed7f96dcfbad4798e376 Related-bug: #1607981
There are some parts of devstack that call the service api to verify the extension list we pass to tempest. This is fine for the out of gate case if it makes life easier for users. But, we should not ever trust this for gate testing. This commit adds a check on master to ensure we always are using the default value of 'all'. On stable we hard code a list of available extensions so this isn't a concern there. Change-Id: I01be3c1392fd4642bdd4633ba5624ddacb608bc5
Both libraries are needed in gate jobs to be able to make sure we don't break the gate broadly. Change-Id: Idb2a766069bbea088d402cb86d7ded86e93f3096 Depends-On: I747480b6063a62e82ca2b030f274d3e87bf28b3b
This commit swaps the argument order of tempest tox jobs that use a regex to specify a subset of tests to run. This is necessary for some future changes to the tempest tox definitions that will switch it from using a testr wrapping bash script to the tempest run command instead. With tempest run you specify a regex with a '--regex' parameter and to keep backwards compatibility this is added to the tempest tox definitions. However this breaks on devstack-gate because we pass the concurrency in before the regex. This ends up having a call equivalent to: tempest run --regex --concurrency=2 $REGEX which obviously is incorrect. Simply switching the arg order should work in both cases. It's also worth pointing out that this is a temporary step as we will migrate devstack-gate to call tempest init and tempest run directly. Change-Id: I8786b9709584378aaf48393115dda94397e22544 Need-by: I3684fce66a799579fa68af119652cafef25a9f03
Change-Id: Ia8801a2aec4211681d42e8295df93188cf03879e
Change-Id: I133f004ec749dfd2c360474936b3421d146c33ab
Change-Id: Iea5045d5f615791bb30ec9f7273a672ff9be5ca1
Change-Id: Icf3d139dfba0b6f77e5a6b6ebf796f75585268f6 Conflicts: devstack-vm-gate-wrap.sh
Remove "FORCE=yes" to align with openstack-infro/devstack-gate upstream Move FLAT_NETWORK_BRIDGE item to pre_test_hook when neutron is used Set gate_hook link to our repo(under $WORKSPACE)'s devstack-vm-gate.sh
There is a workaround which always set multi-hosts for Nova network. It creates a br_flat interface which is connected to vmnet and DHCP server listens on this interface. But XenServer has eth3 connected to vmnet. We should use eth3 as the flat interface otherwise the devstack VM has no access to the guest instances. So we shouldn't apply that workaround for XenServer. And we currently don't use multi-hosts for XenServer CI. So let's skipt it.
|
Can't merge due to the conflicting files - but I'm not sure this is the right way to do things anyway; we've historically done an actual rebase of our custom changes on top of the latest state of the repo. Admittedly that approach does not preserve history well, but it means that we have a strong record of the changes we need for our CI (they are always the last few changes). Thoughts? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.