Add ISS Network Sync class and basic scenario #13543
Merged
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
vsedmik
added
QETestCoverage
|
trigger: test-robottelo |
Comment on lines
+2067
to
+2069
| module_satellite_host.cli.Settings.set( | ||
| {'name': 'subscription_connection_enabled', 'value': 'No'} | ||
| ) |
There was a problem hiding this comment.
Do we need an teardown for this to change back to Yes (if default)?
There was a problem hiding this comment.
No. On the downstream sat we always need this off.
|
trigger: test-robottelo |
pondrejk
approved these changes
Jan 2, 2024
This was referenced Jan 2, 2024
This was referenced Jan 2, 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
Network Sync functionality of ISS hasn't been automated yet, coverage is missing.
Solution
This PR adds new class with first scenario to cover Network Sync. The previous classes will be refactored in one of next PRs since they don't reflect the reality and the change should be CPed deeper than this PR is.
Related Issues
Covers this customer case BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2213128