-
Notifications
You must be signed in to change notification settings - Fork 559
tests: Remove AZ add/remove host integration test #3120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
tests: Remove AZ add/remove host integration test #3120
Conversation
I'm not at all convinced these issues are caused by parallelization. As far as I understand, we do not run the tests in parallel -- we don't use |
Yes, I saw it fail here. Reproducing the failure here:
So, as I'm reading that, a test in another file (meaning |
73f7c95
to
25e93c1
Compare
Go runs tests in parallel for different packages in parallel. The AZ add/remove host test was adding and removing hosts from an AZ and if this ran at the same time as another test that created a server then the host addition or removal would fail since Nova forbids it. There does not appear to be any way to resolve this. We could run all integration tests serially instead, but this would be a backwards step that will massively increase test run time. We could also rewrite the test to only add/remove an unused host, but that would require us to fence off this compute node in all other tests using non-default parameters to server create. Given the lack of better options, we simply remove the test and assume our testing to date on this method has been good enough and unit tests will be enough to carry us forward. Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
25e93c1
to
320542c
Compare
Go runs tests in parallel for different packages in parallel. The AZ add/remove host test was adding and removing hosts from an AZ and if this ran at the same time as another test that created a server then the host addition or removal would fail since Nova forbids it. There does not appear to be any way to resolve this. We could run all integration tests serially instead, but this would be a backwards step that will massively increase test run time. We could also rewrite the test to only add/remove an unused host, but that would require us to fence off this compute node in all other tests using non-default parameters to server create. Given the lack of better options, we simply remove the test and assume our testing to date on this method has been good enough and unit tests will be enough to carry us forward.
Signed-off-by: Stephen Finucane stephenfin@redhat.com