adding the support for ipv4 and ipv6 parameterization for Container and VM #15881
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
jyejare
reviewed
Aug 7, 2024
omkarkhatavkar
force-pushed
the
ipv4_6_parameterization
branch
5 times, most recently
from
061c1a7
to
9bee992
Compare
omkarkhatavkar
added
CherryPick
omkarkhatavkar
force-pushed
the
ipv4_6_parameterization
branch
3 times, most recently
from
56898f9
to
a9c141a
Compare
omkarkhatavkar
force-pushed
the
ipv4_6_parameterization
branch
from
a9c141a
to
cdc8c34
Compare
jyejare
approved these changes
Aug 14, 2024
|
Sanity Test Suite is passed with change including CI link to CI PR |
omkarkhatavkar
force-pushed
the
ipv4_6_parameterization
branch
from
cdc8c34
to
fcca1c7
Compare
This was referenced Aug 20, 2024
omkarkhatavkar
added a commit
to omkarkhatavkar/robottelo
that referenced
this pull request
Aug 21, 2024
5 tasks
Gauravtalreja1
pushed a commit
that referenced
this pull request
Sep 3, 2024
…ntainer and VM (#16004) adding the support for ipv4 and ipv6 parameterization for Container and VM (#15881) (cherry picked from commit ccbb5bd) Co-authored-by: Omkar Khatavkar <[email protected]>
Gauravtalreja1
pushed a commit
that referenced
this pull request
Sep 3, 2024
…ntainer and VM (#16202) adding the support for ipv4 and ipv6 parameterization for Container and VM (#15881) (cherry picked from commit ccbb5bd) Co-authored-by: Omkar Khatavkar <[email protected]>
jyejare
pushed a commit
to jyejare/robottelo
that referenced
this pull request
Oct 19, 2024
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.
Problem Statement
Currently, Content-Host-based test-cases/fixtures are not taking an input/param for network type so that the ipv6 / ipv4 satellite can connect with the ipv6 / ipv4 content host.
But, since broker and Tower support provide the param for choosing the network type, we have to alter the content host tests cases/fixtures to take the argument for the network type parameter.
Solution
As discussed in the brainstorming call on 31st July 2024, we will choose to parameterise tests to provide the network type parameter. That looks like:
@pytest.mark.network_type(['ipv4', 'ipv6'])that as value can also take the regex very similar as rhel_ver_list / rhel_Ver_match implementation.CI PR Dependency
1439
Test Matrix
If there is no marker then it will pick the network based on the Satellite.