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

Add readiness checks to registry operator integration tests #1238

Closed
3 tasks
Tracked by #1523
michael-valdron opened this issue Aug 31, 2023 · 3 comments
Closed
3 tasks
Tracked by #1523

Add readiness checks to registry operator integration tests #1238

michael-valdron opened this issue Aug 31, 2023 · 3 comments
Labels
area/registry Devfile registry for stacks and infrastructure good first issue Good for newcomers lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. lifecycle/stale Stale items. These items have not been updated for 90 days.

Comments

@michael-valdron
Copy link
Member

Which area/kind this issue is related to?

/area registry

Issue Description

The integration tests need readiness checks to ensure pods are ready before proceeding, currently only active checks exist to ensure the pod is running before proceeding. This at times causes test cases to fail if the pods are not ready in time, most commonly if the registry operator itself needs deployment during the initial run of the test suite.

Acceptance Criteria

  • Add readiness check function to integration test suite client package
  • Add readiness check function invoke for deploying the registry operator
  • Add readiness check function invoke for the devfile registry test deployments
@openshift-ci openshift-ci bot added the area/registry Devfile registry for stacks and infrastructure label Aug 31, 2023
@michael-valdron
Copy link
Member Author

Prior discussion: #1106 (comment)

@michael-valdron michael-valdron moved this to Backlog in Devfile Project Aug 31, 2023
@michael-valdron michael-valdron moved this from Backlog to Refinement in Devfile Project Nov 28, 2023
Copy link

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Nov 30, 2023
@michael-valdron michael-valdron added good first issue Good for newcomers and removed lifecycle/stale Stale items. These items have not been updated for 90 days. labels Dec 21, 2023
Copy link

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Sep 21, 2024
@github-actions github-actions bot added the lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. label Nov 21, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 21, 2024
@github-project-automation github-project-automation bot moved this from Refinement to Done ✅ in Devfile Project Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry Devfile registry for stacks and infrastructure good first issue Good for newcomers lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. lifecycle/stale Stale items. These items have not been updated for 90 days.
Projects
Status: Done ✅
Development

No branches or pull requests

1 participant