Add S2I speculative deploy testing for telemetry-operator - #992
Conversation
|
Skipping CI for Draft Pull Request. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Team Run ID: Comment |
|
@danpawlik hey Daniel until they get merged, you need depends-on to openstack-k8s-operators/s2i-openstack-containers#91 and openstack-k8s-operators/ci-framework#4131 |
|
This change depends on a change that failed to merge. Change openstack-k8s-operators/ci-framework#4131 is needed. |
|
This change depends on a change that failed to merge. Change openstack-k8s-operators/ci-framework#4131 is needed. |
|
recheck |
|
Build failed (check pipeline). Post ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 2h 45m 17s |
(The ceph failure is well known =( ) |
|
|
||
| - job: | ||
| name: s2i-speculative-deploy-test-telemetry | ||
| parent: telemetry-operator-multinode-autoscaling |
There was a problem hiding this comment.
This parent doesn't actually run any tests.
Better parent is: functional-tests-osp18, which runs tempest and FVTs for logging, autoscaling.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: danpawlik, rebtoor The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
This seems OK, as long as the CI passes. One thing though... I see this is testing Aodh and Cloudkitty is deferred, what about Ceilometer? |
With ceilometer would be done in another story - OSPRH-34556 - as Ceilometer would use 2 images not 4. |
|
/test precommit-check |
|
/test telemetry-operator-build-deploy |
|
New changes are detected. LGTM label has been removed. |
|
This change depends on a change that failed to merge. Change #993 is needed. |
|
recheck |
|
@rebtoor @elfiesmelfie fun fact: since when I changed in |
Implement similar S2I testing workflow as watcher-operator [1] that adds: - s2i-speculative-deploy-test-telemetry job - validates speculatively-built S2I telemetry-operator container images against a live OpenStack deployment with telemetry enabled - s2i-openstack-container-content-provider job - builds S2I containers - Non-voting github-check jobs to validate S2I builds before merging This enables testing whether speculatively-rebuilt telemetry container images function correctly in real deployments. Cloudkitty s2i (cloudkitty/cloudkitty-api) deferred: the cloudkitty deploy path pulls the meta content provider, which conflicts with s2i image injection. Add when a clean deploy path exists. [1] openstack-k8s-operators/watcher-operator#443 Related-To: OSPRH-34558 Assisted-By: Claude Haiku 4.5 <noreply@anthropic.com> Depends-On: openstack-k8s-operators/ci-framework#4131 Depends-On: openstack-k8s-operators#993 Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
|
|
recheck |
|
Build failed (check pipeline). Post ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 3h 51m 29s |
|
recheck |
|
This change depends on a change that failed to merge. Change openstack-k8s-operators/ci-framework#4152 is needed. |
|
recheck |
|
/test telemetry-operator-build-deploy |
|
recheck |
|
/test telemetry-operator-build-deploy |
|
@danpawlik: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
Build failed (check pipeline). Post ❌ telemetry-openstack-meta-content-provider-master FAILURE in 12m 31s |
|
recheck |
2 similar comments
|
recheck |
|
recheck |
|
Centos stream container images were broken new images seems to work: |
|
recheck |
4 participants
Implement similar S2I testing workflow as watcher-operator [1] that adds:
This enables testing whether speculatively-rebuilt telemetry container images function correctly in real deployments.
Cloudkitty s2i (cloudkitty/cloudkitty-api) deferred: the cloudkitty deploy path pulls the meta content provider, which conflicts with s2i image injection. Add when a clean deploy path exists.
[1] openstack-k8s-operators/watcher-operator#443
Related-To: OSPRH-34558
Related-To: OSPRH-34557
Assisted-By: Claude Haiku 4.5 noreply@anthropic.com
Depends-On: openstack-k8s-operators/ci-framework#4131
Depends-On: #993
optional
Depends-On: openstack-k8s-operators/ci-framework#4152