[ci] Speculative s2i cinder deploy via OpenStackVersion - #711
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
|
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: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Zuul encountered a syntax error while parsing its Invalid Ansible variable name '_s2i_cinder_scalar_images' for dictionary value @ data['vars'] The problem appears in the "s2i-speculative-deploy-test-cinder" job stanza: job: in "openstack-k8s-operators/cinder-operator/zuul.d/jobs.yaml@main", line 48 |
de8bba4 to
7eded60
Compare
|
This change depends on a change that failed to merge. Change openstack-k8s-operators/s2i-openstack-containers#91 is needed. |
|
recheck |
7eded60 to
ae19640
Compare
Add cinder-s2i-content-provider (child of the s2i content provider) and cinder-s2i-tempest (child of cinder-operator-tempest) so github-check builds s2i cinder images and applies them through cifmw_set_containers_images during edpm_prepare. Keep the operator content provider for the catalog and append the s2i registry so CRC can pull both. cinder-volume is applied as cinderVolumeImages.volume1 because OpenStackVersion stores volume backends as a map. Depends-On: openstack-k8s-operators/s2i-openstack-containers#91 Depends-On: openstack-k8s-operators/ci-framework#4131 Co-authored-by: Cursor <cursoragent@cursor.com>
ae19640 to
dc2596f
Compare
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 14m 55s |
|
The controlplane has been patched to consume images from the s2i content provider: The failure is probably caused by ceph and solved by openstack-k8s-operators/ci-framework#4130 . Retesting it with a depends-on. |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 46m 16s |
|
recheck |
|
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
|
recheck |
|
|
||
| - job: | ||
| name: cinder-s2i-tempest | ||
| parent: cinder-operator-tempest |
There was a problem hiding this comment.
Instead of inheriting from the existing tempest job, I think we should have a generic base parent job for such tests. Not all repositories may have an existing tempest job.
So the idea would be to define a generic job, currently inheriting from podified-multinode-hci-deployment-crc-1comp-backends, which would define most of the variables, for sure cifmw_crc_additional_insecure_registries, cifmw_crc_additional_allowed_registries and the default value of cifmw_set_containers_images, which would combine the part which we want in all jobs ("scalar OpenStackVersion fields from the s2i provider") plus an optional part, say cifmw_set_containers_images_extra, that some jobs like this cinder or manila one can override.
There was a problem hiding this comment.
I'm going to refine it and it probably does not work now, but this is a draft with the split parent job:
There was a problem hiding this comment.
In addition/extending what I wrote above, two other points (I've mentioned them privately but better have them here too):
- I think we would need that generic job as "root" job as described above, but not based on podified-multinode-hci-deployment-crc-1comp-backends, but rather without ceph; and a secondary one with ceph.
- also, the variable which defines the additional containers (like cinder-volume and manila-share) could be just defined as a list/dictionary of names as it was before, and the base jobs should do the magic of changing the list into the appropriate structure. This would simplify the definition of the derived jobs.
Summary
cinder-s2i-content-provider, a child ofs2i-openstack-container-content-provider, with an explicit cinder image list (cinder-api,cinder-backup,cinder-scheduler,cinder-volume).cinder-s2i-tempest, a child ofcinder-operator-tempest, that applies those s2i images to OpenStackVersion duringedpm_prepareviacifmw_set_containers_images.cinderVolumeImages.volume1for the HCI CinderVolume (volume backends are a map, not a scalar).Test plan
cinder-s2i-content-providerandcinder-s2i-tempest(voting: false)customContainerImagesincludes s2icinderAPIImage,cinderBackupImage,cinderSchedulerImage, andcinderVolumeImages.volume1cinder-operator-kuttlandcinder-operator-tempeststill consume only the operator content provider