[DNM] test tempest#3829
Conversation
|
Skipping CI for Draft Pull Request. |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/b9c4995c6eb84cd6adec2560c34fb413 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 20m 10s |
The Jinja2 join("\n") inside a YAML block scalar produces a literal
two-character \n instead of an actual newline. This caused
discover-tempest-config to fail with "An odd number of override
options was found" because the last scenario override and the
controller IP override were concatenated on a single line.
Use a YAML double-quoted variable (_nl: "\n") where the YAML parser
correctly interprets the escape sequence as a real newline character.
Made-with: Cursor
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/3dd2faac9b2944a89bd0df9724ed8488 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 20m 51s |
When kubernetes.core.k8s_info returns an error (API timeout, transient connectivity loss), the result dict lacks the .resources key, causing the until condition and summary vars to fail with 'dict object has no attribute resources'. Add defensive checks so the retry loop continues on transient errors instead of aborting. Made-with: Cursor
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/b2ec697be00b46cdb7cd05fed6329b38 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 12m 39s |
When all 4 Tempest CRs include the same extraImages with a fixed ID, only the first pod to reach image creation succeeds. The rest get a 409 Conflict, leaving IMAGE_ID empty and causing a 600s timeout loop. Only include extraImages in the first CR (index 0). The other pods skip image creation and find the image already active in Glance by the time their tests start. Made-with: Cursor
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/d75bf645521d4874a5526fd490622416 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 07m 01s |
When all 4 pods run discover-tempest-config --create simultaneously, they race on creating shared Nova flavors (m1.micro, m1.nano) causing 409 Conflict and exit 123 before any tests run. Fix: only the first CR gets tempestconfRun.create=true. The remaining 3 CRs get create=false (discover-only, no resource creation). The first CR is applied 120s before the rest, ensuring images and flavors exist in Glance/Nova when the other pods discover the cloud. Made-with: Cursor
|
[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 https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/b96895c09b294a01a3d1ff59bb1a961d ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 19m 08s |
WIP