Skip to content

Enable defaulting of nova in kuttle job #921

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

mrkisaolamb
Copy link
Contributor

@mrkisaolamb mrkisaolamb commented Feb 5, 2025

@openshift-ci openshift-ci bot requested review from gibizer and kk7ds February 5, 2025 10:50
@openshift-ci openshift-ci bot added the approved label Feb 5, 2025
Copy link

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/231ce90da53b4df8960ae8113279286b

✔️ openstack-meta-content-provider SUCCESS in 2h 55m 34s
nova-operator-kuttl RETRY_LIMIT in 30m 30s
✔️ nova-operator-tempest-multinode SUCCESS in 2h 25m 47s
✔️ nova-operator-tempest-multinode-ceph SUCCESS in 2h 38m 15s

Copy link

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/d204e1b3b52f4e2f9da2ea9db4fbd04c

✔️ openstack-meta-content-provider SUCCESS in 2h 54m 11s
nova-operator-kuttl RETRY_LIMIT in 31m 22s
✔️ nova-operator-tempest-multinode SUCCESS in 2h 36m 36s
nova-operator-tempest-multinode-ceph FAILURE in 1h 27m 30s

Copy link

Zuul encountered a syntax error while parsing its
configuration in the repo openstack-k8s-operators/nova-operator on branch main. The
problem was:

extra keys not allowed @ data['post_deploy']

The problem appears in the the "nova-operator-kuttl" job stanza:

job:
name: nova-operator-kuttl
parent: cifmw-multinode-kuttl-operator-target
dependencies: ["openstack-meta-content-provider"]
roles:
- zuul: github.com/openstack-k8s-operators/ci-framework
description: |
This job deploy a basic "Compute Starter Kit" topology
https://www.openstack.org/software/sample-configs#compute-starter-kit
...

in "openstack-k8s-operators/nova-operator/.zuul.yaml@main", line 2

Copy link

Zuul encountered a syntax error while parsing its
configuration in the repo openstack-k8s-operators/nova-operator on branch main. The
problem was:

Invalid Ansible variable name 'post-run' for dictionary value @ data['vars']

The problem appears in the the "nova-operator-kuttl" job stanza:

job:
name: nova-operator-kuttl
parent: cifmw-multinode-kuttl-operator-target
dependencies: ["openstack-meta-content-provider"]
roles:
- zuul: github.com/openstack-k8s-operators/ci-framework
description: |
This job deploy a basic "Compute Starter Kit" topology
https://www.openstack.org/software/sample-configs#compute-starter-kit
...

in "openstack-k8s-operators/nova-operator/.zuul.yaml@main", line 2

@mrkisaolamb mrkisaolamb force-pushed the kuttl_fix branch 2 times, most recently from 4a6885f to 691568d Compare February 11, 2025 16:45
Copy link

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/50f46ddde56e4db2bb5508e47e5c46d2

✔️ openstack-meta-content-provider SUCCESS in 3h 54m 57s
nova-operator-kuttl RETRY_LIMIT in 21m 38s
✔️ nova-operator-tempest-multinode SUCCESS in 2h 23m 30s
✔️ nova-operator-tempest-multinode-ceph SUCCESS in 2h 41m 10s

@mrkisaolamb mrkisaolamb force-pushed the kuttl_fix branch 4 times, most recently from 379b8e1 to 67a7e0b Compare February 12, 2025 14:23
@mrkisaolamb
Copy link
Contributor Author

/retest

Copy link

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/ea87f35769074a5fb4cdff8ba7c7d70e

✔️ openstack-meta-content-provider SUCCESS in 5h 39m 34s
nova-operator-kuttl FAILURE in 36m 02s
✔️ nova-operator-tempest-multinode SUCCESS in 2h 09m 58s
✔️ nova-operator-tempest-multinode-ceph SUCCESS in 2h 51m 48s

Copy link

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/355c453b32624f82acb9bd721bb030fc

✔️ openstack-meta-content-provider SUCCESS in 3h 20m 57s
nova-operator-kuttl FAILURE in 34m 58s
nova-operator-tempest-multinode FAILURE in 1h 24m 09s
✔️ nova-operator-tempest-multinode-ceph SUCCESS in 2h 48m 58s

Copy link

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/2d9be82c258b4f9ab501aa6d44a85fde

✔️ openstack-meta-content-provider SUCCESS in 3h 52m 12s
nova-operator-kuttl POST_FAILURE in 33m 40s
✔️ nova-operator-tempest-multinode SUCCESS in 2h 19m 50s
✔️ nova-operator-tempest-multinode-ceph SUCCESS in 2h 56m 21s

Copy link

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/59e573377d4e43fb9056be89bf5a4ac2

✔️ openstack-meta-content-provider SUCCESS in 2h 38m 01s
nova-operator-kuttl FAILURE in 35m 33s
✔️ nova-operator-tempest-multinode SUCCESS in 2h 17m 00s
nova-operator-tempest-multinode-ceph FAILURE in 1h 34m 49s

Copy link

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/29b60a0ca6ec4aa2aa83ee4a0ba5715a

✔️ openstack-meta-content-provider SUCCESS in 1h 42m 07s
nova-operator-kuttl FAILURE in 35m 29s
nova-operator-tempest-multinode FAILURE in 1h 21m 18s
nova-operator-tempest-multinode-ceph FAILURE in 1h 24m 48s

Copy link

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/d94f3c6b1d2b4a5fbd3f1ff5c92deaf8

✔️ openstack-meta-content-provider SUCCESS in 2h 53m 03s
nova-operator-kuttl FAILURE in 32m 49s
✔️ nova-operator-tempest-multinode SUCCESS in 2h 21m 03s
✔️ nova-operator-tempest-multinode-ceph SUCCESS in 2h 35m 54s

Copy link

This change depends on a change that failed to merge.

Change openstack-k8s-operators/ci-framework#2735 is needed.

@mrkisaolamb
Copy link
Contributor Author

recheck

Copy link
Contributor

@SeanMooney SeanMooney left a comment

Choose a reason for hiding this comment

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

/lgtm

i agree with these updates we should merge this once the depnecy is merged

@@ -138,12 +138,10 @@ metadata:
name: nova-kuttl-api-0
status:
containerStatuses:
- image: quay.io/podified-antelope-centos9/openstack-nova-api:current-podified
Copy link
Contributor

Choose a reason for hiding this comment

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

ah you removed this becuase it may come form the content provider i assume

ya that makes sense to remove

@SeanMooney
Copy link
Contributor

im only adding hold to this because the depnecy has not merged

once that is merged feel free to drop the hold lable

@mrkisaolamb
Copy link
Contributor Author

recheck

@SeanMooney
Copy link
Contributor

SeanMooney commented Feb 20, 2025

we need to do one more rdo un with rdo-check too because the current one has #927 included
recheck wont work while its still running so we need to wait for it complete first unless you want to just rebase
that will kick it from the queue and retrigger the job

.zuul.yaml Outdated
@@ -181,7 +189,8 @@
github-check:
jobs:
- openstack-meta-content-provider
- nova-operator-kuttl
- nova-operator-kuttl:
override-checkout: main
Copy link
Contributor

Choose a reason for hiding this comment

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

what does this mean? Will this prevent testing the content of the nova-operator PR the job is triggered on?

Copy link
Contributor

Choose a reason for hiding this comment

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

IIUC https://zuul-ci.org/docs/zuul/latest/config/job.html#attr-job.override-checkout right, that picks the main branches for other involved projects

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

Makefile Outdated
@@ -428,3 +429,11 @@ PHONY: crd-schema-check
crd-schema-check: manifests
INSTALL_DIR=$(LOCALBIN) CRD_SCHEMA_CHECKER_VERSION=$(CRD_SCHEMA_CHECKER_VERSION) hack/build-crd-schema-checker.sh
INSTALL_DIR=$(LOCALBIN) BASE_REF="$${PULL_BASE_SHA:-$(BRANCH)}" hack/crd-schema-checker.sh


.PHONY: nova
Copy link
Contributor

Choose a reason for hiding this comment

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

I would use a bit more descriptive name. We have a run target that runs the operator from the git repo. So this would be something like run_with_olm

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

tasks:
- name: Scale down deployment
ansible.builtin.shell: |
oc patch csv -n openstack-operators openstack-operator.v0.0.1 --type json -p="[{"op": "replace", "path": "/spec/install/spec/deployments/0/spec/replicas", "value": "0"}]"
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm wondering if we can always rely on the csv name being v0.0.1

Copy link
Contributor

@bogdando bogdando Feb 20, 2025

Choose a reason for hiding this comment

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

That is a good question, but CSV versioning questions are in flux as yet. Let's copy what other projects do for the time being.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

so IMO we can go with openstack-operator.v0.0.1

chdir: "{{ ansible_user_dir }}/src/github.com/openstack-k8s-operators/nova-operator"
script: make nova
extra_args:
CATALOG_IMAGE: "{{ nova_catalog_image | default('quay.io/openstack-k8s-operators/nova-operator-index:latest') }}"
Copy link
Contributor

Choose a reason for hiding this comment

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

I guess nova_catalog_name is here to ensure that the nova-operator that is built from this PR will be used for the deployment. Who sets this variable?

chdir: "{{ ansible_user_dir }}/src/github.com/openstack-k8s-operators/nova-operator"
script: make nova
extra_args:
CATALOG_IMAGE: "{{ nova_catalog_image | default('quay.io/openstack-k8s-operators/nova-operator-index:latest') }}"
Copy link
Contributor

Choose a reason for hiding this comment

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

The default here seems to be a duplication as CATALOG_IMAGE is already defaulted in the makefile.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

Copy link

This change depends on a change that failed to merge.

Change #927 is needed.

@gibizer
Copy link
Contributor

gibizer commented Feb 20, 2025

Copy link

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/f443106e47bd4d09819a39a07df484e6

✔️ openstack-meta-content-provider SUCCESS in 2h 46m 55s
✔️ nova-operator-kuttl SUCCESS in 44m 53s
nova-operator-tempest-multinode FAILURE in 1h 28m 01s
nova-operator-tempest-multinode-ceph FAILURE in 2h 23m 40s

@SeanMooney
Copy link
Contributor

in #928 i have taken this pr and added a patch to drop the edpm josb and enable debug on the pipeline i also have removed #921

that should give us more info about why its not working without that.

@SeanMooney
Copy link
Contributor

im not 100% sure but i think the actually issue is how we configure implied branches
so we could trigger jobs on opendev master
i belive will fix the issue for fr1 and main for now
#929

and we can then alter how we make the teampels work withopen dev on main
there are other ways to make that towrk i think but i belive that the cause of the current issue with fr1 job content running on main

we are declaring on fr1 that the job definition fr1 is actually for main

https://zuul-ci.org/docs/zuul/latest/config/pragma.html#attr-pragma.implied-branches

https://imgur.com/a/cjtmZL6

zuul should not have 2 job definition with the same name of rht same branch like that
the fr2 variant should have fr2 as the branch

I'm 99% sure that because of

  • pragma:
    implied-branch-matchers: True
    implied-branches:
    - main
    - master

@mrkisaolamb
Copy link
Contributor Author

recheck

Copy link

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://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/fd567916c30b454c890cfd3804a211f4

✔️ openstack-meta-content-provider SUCCESS in 2h 54m 31s
✔️ nova-operator-kuttl SUCCESS in 41m 14s
nova-operator-tempest-multinode FAILURE in 1h 24m 29s
✔️ nova-operator-tempest-multinode-ceph SUCCESS in 2h 37m 24s

@mrkisaolamb
Copy link
Contributor Author

recheck

Copy link
Contributor

@SeanMooney SeanMooney left a comment

Choose a reason for hiding this comment

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

/lgtm we agreed to adress the underlying issue in a follow up.

ill remove hold when the dependcies are merged

@openshift-ci openshift-ci bot added the lgtm label Feb 24, 2025
Copy link
Contributor

openshift-ci bot commented Feb 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mrkisaolamb, SeanMooney

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

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [SeanMooney,mrkisaolamb]

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

@openshift-merge-bot openshift-merge-bot bot merged commit e1e2ba8 into openstack-k8s-operators:main Feb 24, 2025
7 checks passed
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.

5 participants