Automate TC 28597 : Telemetry info on migration #86
Conversation
This file contains hidden or 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
hu-weihua
changed the title
hu-weihua
changed the title
Contributor
|
@hu-weihua @sergiordlr Can we rebase this one? Do we want this test on the upstream CI batch? We need to implement a way to discriminate tests only for a single CAM release based on tags otherwise some jobs might attempt and fail on older releases, this is on me. |
Contributor
Author
|
@fbladilo I have remove the role of this case from |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is automatic test case for TC28597
This test case is used to test CAM and Prometheus integration. Customer can leverage this feature to have better visibility on how successful when migrating their applications.
After deploying CAM (version >=1.1.2),
The steps of TC28597 are
openshift.io/cluster-monitoring: "true"to namespaceopenshift-migrationservice/mig-controller-metricsis runningmetricscan be expose from APIhttp://mig-controller-metrics.openshift-migration.svc.cluster.local:2112/metricsmetricsfrom OCP monitoring prometheus web console. this step won't be covered by automation.