Repository navigation
Conversation
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? |
|
Build succeeded (check pipeline). ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 24m 12s Warning: |
34d9861 to
0b04252
Compare
Reuse the existing s2i content provider's speculative bootc image rather than build it again or allocate another paused provider. Select the exact published reference and pass it to ci-framework's prebuilt-image consumer, which handles qcow2 packaging, registry access, and bare-metal deployment. Combine files and irrelevant-files filters so deployment coverage follows bootc and base-image inputs plus shared build and CI tooling, while excluding documentation-only changes. Add contract tests for provider reuse, image selection, cached handoff, and file filtering, and retain the base-before-bootc build test. Select native nmstate for CS10 bootc deployment and cover that selection in the provider contract tests. Use install_yamls nmstate_baremetal scenario wiring so the selected tool receives a matching network template. Jira: OSPRH-40388 Depends-On: openstack-k8s-operators/ci-framework#4331 Depends-On: openstack-k8s-operators/install_yamls#1211 Co-Authored-By: GPT-6.1 Sol <noreply@openai.com> Signed-off-by: James Slagle <jslagle@redhat.com>
Add the speculative s2i-openstack-containers checkout to the CS10 content provider and enable the s2i bootc build path supplied by ci-framework. Keep the existing parent and other settings so operator and non-bootc images continue to be built as before. Select native nmstate for the CS10 bootc deployment job using the install_yamls nmstate_baremetal scenario, avoiding the os-net-config executable that is not included in the CS10 bootc image. Jira: OSPRH-40389 Depends-On: openstack-k8s-operators/ci-framework#4331 Depends-On: openstack-k8s-operators/install_yamls#1211 Co-Authored-By: GPT-6.1 Sol <noreply@openai.com> Signed-off-by: James Slagle <jslagle@redhat.com>
|
Build succeeded (check pipeline). ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 58m 33s Warning: |
Reuse the existing s2i content provider's speculative bootc image rather than build it again or allocate another paused provider. Select the exact published reference and pass it to ci-framework's prebuilt-image consumer, which handles qcow2 packaging, registry access, and bare-metal deployment. Combine files and irrelevant-files filters so deployment coverage follows bootc and base-image inputs plus shared build and CI tooling, while excluding documentation-only changes. Add contract tests for provider reuse, image selection, cached handoff, and file filtering, and retain the base-before-bootc build test. Select native nmstate for CS10 bootc deployment and cover that selection in the provider contract tests. Use install_yamls nmstate_baremetal scenario wiring so the selected tool receives a matching network template. Jira: OSPRH-40388 Depends-On: openstack-k8s-operators/ci-framework#4331 Depends-On: openstack-k8s-operators/install_yamls#1211 Co-Authored-By: GPT-6.1 Sol <noreply@openai.com> Signed-off-by: James Slagle <jslagle@redhat.com>
0b04252 to
98e8533
Compare
|
[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 |
98e8533 to
57d3899
Compare
…mers Build CS10 bootc host images from the speculative s2i checkout using its build.sh entry point, including the base dependency. Keep this path opt-in so CS9 consumers continue using edpm-image-builder, and recognize s2i changes when selecting builds and image tags. Allow deployment consumers to pull an existing bootc image into root container storage and reuse qcow2 conversion, packaging, publication, and extraction smoke tests without rebuilding the host image or adding another paused content provider. Keep packaging controller-local. Configure registry access in the normal baremetal deployment flow after its existing CRC inventory and SSH setup. Use the controller kubeconfig for API updates and delegate only CRI-O configuration to CRC, avoiding duplicate SSH host-key setup or API credential copies. Enable this step only for the prebuilt-image consumer. Test build/import commands, controller-local packaging, preservation of deployment inputs, registry parameter validation, and deployment ordering. Jira: OSPRH-40386 Co-Authored-By: GPT-6.1 Sol <noreply@openai.com> Signed-off-by: James Slagle <jslagle@redhat.com>
57d3899 to
f44d781
Compare
|
Build succeeded (check pipeline). ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 37m 38s Warning: |
Build CS10 bootc host images from the speculative
s2i-openstack-containers checkout using its build.sh entry point,
including the base image dependency. Keep builds in root container
storage and reuse the existing qcow2 generation, packaging, and
publication contract.
Keep the s2i path opt-in so existing CS9 consumers continue building
from edpm-image-builder. Add a reusable CS10 provider, recognize s2i
changes when selecting builds and tags, and test the build arguments and
local image handoff with mock commands.
Jira: OSPRH-40386
Co-Authored-By: GPT-6.1 Sol noreply@openai.com
Signed-off-by: James Slagle jslagle@redhat.com