-
Notifications
You must be signed in to change notification settings - Fork 115
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
Fix for teardown failures #16211
Fix for teardown failures #16211
Conversation
trigger: test-robottelo |
PRT Result
|
3 tests using VMs passed, 3 using docker failed with different error. |
trigger: test-robottelo |
trigger: test-robottelo |
PRT Result
|
@vsedmik thank you for providing and testing the fix! |
(cherry picked from commit 36f2ecc)
Fix for teardown failures (#16211) (cherry picked from commit 36f2ecc) Co-authored-by: vsedmik <[email protected]>
Problem Statement
#15931 broke teardown of tests which use contenthosts registered through a Capsule because the registration target (where the host is registered to, Capsule in this case) was assigned to the host's
self.satellite
here, and in teardown we try to search and delete the host here, which fails since Capsule has no APISolution
As per @ogajduse++ proposal, provide the Satellite instance in host's
self.satellite
instead of the registration target (Capsule) so that it can be searched and destroyed at the Sat side.PRT test Cases example
trigger: test-robottelo
pytest: tests/foreman/cli/test_host.py -k test_host_registration_with_capsule_using_content_coherence