[multiple] Log patched container images for OpenStackVersion CR - #4152
[multiple] Log patched container images for OpenStackVersion CR#4152danpawlik wants to merge 1 commit into
Conversation
|
Skipping CI for Draft Pull Request. |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 25m 59s |
|
Test done: openstack-k8s-operators/telemetry-operator#992 |
PR Summary by QodoLog OpenStackVersion custom container image overrides
AI Description
Diagram
High-Level Assessment
Files changed (2)
|
|
recheck |
Code Review by Qodo
1. edpm_prepare variables misnamed
|
336fbba to
384e377
Compare
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 30m 15s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 34m 19s |
|
after update: |
|
recheck |
384e377 to
1b8e48e
Compare
1b8e48e to
ae35af1
Compare
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 Depends-On: openstack-k8s-operators/tcib#418 Optionally: Depends-On: openstack-k8s-operators/ci-framework#4152 Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 26m 55s |
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 Depends-On: openstack-k8s-operators/tcib#418 Depends-On: infrawatch/feature-verification-tests#439 Optionally: Depends-On: openstack-k8s-operators/ci-framework#4152 Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
|
recheck |
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
When a job patches the `OpenStackVersion` `controlplane` CR with custom container images (e.g. s2i-built images from an operator PR), the resulting `spec.customContainerImages` is only visible by inspecting the must-gather `openstackversions.core.openstack.org/controlplane.yaml`. Jobs like `s2i-speculative-deploy-test-*` gave no in-log indication of which images were applied. Add a debug task in both `OpenStackVersion` writers -- the `update_containers` role (template + `oc apply`) and the `set_containers` call in `edpm_prepare` -- that reads back the generated CR and prints it verbatim, so the patched images are visible directly in the job output. The rendered file is printed as raw lines rather than re-parsed with `from_yaml`, which threw `yaml.scanner.ScannerError` on values containing a colon-space sequence. Assisted-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
ae35af1 to
8099b1d
Compare
|
New changes are detected. LGTM label has been removed. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 45m 14s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 4h 58m 48s |
|
recheck |
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 Depends-On: openstack-k8s-operators/tcib#418 Depends-On: infrawatch/feature-verification-tests#438 Depends-On: openstack-k8s-operators#998 Depends-On: openstack-k8s-operators/ovn-operator#632 Depends-On: openstack-k8s-operators/edpm-ansible#1268 Optionally: Depends-On: openstack-k8s-operators/ci-framework#4152 Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 54m 52s |
|
recheck |
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 Depends-On: openstack-k8s-operators/tcib#418 Depends-On: infrawatch/feature-verification-tests#439 Depends-On: openstack-k8s-operators#998 Depends-On: openstack-k8s-operators/ovn-operator#632 Depends-On: openstack-k8s-operators/edpm-ansible#1268 Optionally: Depends-On: openstack-k8s-operators/ci-framework#4152 Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 22m 29s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 36m 33s |
|
recheck |
When a job patches the
OpenStackVersioncontrolplaneCR with custom container images (e.g. s2i-built images from an operator PR), the resultingspec.customContainerImagesis only visible by inspecting the must-gatheropenstackversions.core.openstack.org/controlplane.yaml. Jobs likes2i-speculative-deploy-test-*gave no in-log indication of which images were applied.Add a debug task in both
OpenStackVersionwriters -- theupdate_containersrole (template +oc apply) and theset_containerscall inedpm_prepare-- that reads back the generated CR and prints thecustomContainerImagesmap, so the patched images are visible directly in the job output.Assisted-By: Claude Opus 4.8 noreply@anthropic.com