Skip to content
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

Automate TC 28597 : Telemetry info on migration #86

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

hu-weihua
Copy link
Contributor

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

  • Add label openshift.io/cluster-monitoring: "true" to namespace openshift-migration
  • Check if service/mig-controller-metrics is running
  • Check if metrics can be expose from API http://mig-controller-metrics.openshift-migration.svc.cluster.local:2112/metrics
  • Check if can query metrics from OCP monitoring prometheus web console. this step won't be covered by automation.

@hu-weihua hu-weihua changed the title [DO NOT MERGE] Automate TC 28597 [DO NOT MERGE] Automate TC 28597 : Telemetry info on migration Apr 14, 2020
@hu-weihua hu-weihua changed the title [DO NOT MERGE] Automate TC 28597 : Telemetry info on migration Automate TC 28597 : Telemetry info on migration Apr 15, 2020
@fbladilo
Copy link
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.

@hu-weihua
Copy link
Contributor Author

@fbladilo I have remove the role of this case from e2e_mig_samples.yml.
I think it won't impact CI test. But in QE team internal test. we can use this one.
What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants