This repository has been archived by the owner on Apr 7, 2022. It is now read-only.
[1LP][RFR] Fixing TC v2v_custom_attribute #10136
Merged
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.
Signed-off-by: mnadeem92 mnadeem@redhat.com
The Test case was failing as the resources flavor and security group are not available to the cluster.
The Test case is to test the custom attribute flavor and security group by providing a new value for these params other than the default one.
security-group:
default --> provider.data.security_groups.admin[0]
custom value --> provider.data.security_groups.admin[1]
flavor
default --> provider.data.flavors[0]
custom value --> provider.data.flavors[1]
As per TC requirement, we are not required to change the cluster, however in TC cluster gets changed from "admin" to "on-qa" , However the above security-group and flavor is a part of "admin" project and not available in on-qa cluster, This was the main reason for TC failure.
This PR fixing this issue.
{{ pytest: cfme/tests/v2v/test_v2v_migrations_ui.py -k "test_v2v_custom_attribute" --use-provider osp13-ims --use-provider vsphere67-ims --provider-limit 2 -v }}