Skip to content

[DNM] Move placement kuttl tests under default kuttl namespace#1125

Closed
amartyasinha wants to merge 1 commit into
openstack-k8s-operators:mainfrom
amartyasinha:fix_kuttl
Closed

[DNM] Move placement kuttl tests under default kuttl namespace#1125
amartyasinha wants to merge 1 commit into
openstack-k8s-operators:mainfrom
amartyasinha:fix_kuttl

Conversation

@amartyasinha

Copy link
Copy Markdown
Contributor

Currently, zuul only runs default kuttl tests, thus placement kuttl tests were not getting validated. This commit ensure they are also tested.

@openshift-ci

openshift-ci Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci

openshift-ci Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: amartyasinha

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved label Jun 5, 2026
Currently, zuul only runs default kuttl tests, thus placement kuttl tests were not getting validated. This commit ensure they are also tested.

Signed-off-by: Amartya Sinha <amsinha@redhat.com>
@centosinfra-prod-github-app

Copy link
Copy Markdown

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/rdoproject.org/buildset/528c1333b0de451bbac8c3a0d9069898

✔️ openstack-meta-content-provider SUCCESS in 2h 58m 10s
nova-operator-kuttl RETRY_LIMIT in 6m 02s
✔️ nova-operator-tempest-multinode SUCCESS in 2h 27m 29s
✔️ nova-operator-tempest-multinode-ceph SUCCESS in 2h 38m 40s

kind: Namespace
metadata:
name: nova-kuttl-multi-cell
name: nova-kuttl-default

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so each test suite is ment ot have its onw namespace
and nova and palcmenet shoudl not share oen.

serviceUser: placement
status:
databaseHostname: openstack.placement-kuttl-tests.svc
databaseHostname: openstack.nova-kuttl-default.svc

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so this is incorrect

the placement test are a diffent test quite and shoudl eb using ther own nameapces.

you shoudl be able to run the palcemetn test and the nova tests at the same time without them interfering with each other

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @SeanMooney! I can try looking how to enable both tests run in zuul instead of consolidating them in single namespace. The reason I was trying to move placement tests under default namespace was because the cyborg tests are also defined under kuttl/test-suites/default. But yeah, I understand the placement tests are different than nova/cyborg.

@amartyasinha

Copy link
Copy Markdown
Contributor Author

Closing for now. Will check soon how to run both kuttl tests in zuul.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants