-
Notifications
You must be signed in to change notification settings - Fork 12
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
DNM: [zuul] Test changes with zuul #429
Conversation
check-rdo |
d5221c3
to
75eeb55
Compare
Zuul encountered a syntax error while parsing its configuration in the Configuration item has more than one key. Each zuul.yaml
Ensure that every item in the list is a dictionary with only The incorrect values are around: project: null |
75eeb55
to
d63b379
Compare
Zuul encountered a syntax error while parsing its configuration in the The nodeset "centos-9-stream-crc-xxl" was not found. The error appears in the following job stanza: job:
in "infrawatch/service-telemetry-operator/.zuul.yaml@master", line 2, column 3 |
d63b379
to
0683b75
Compare
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/cf196059462a434680064eb4398b0592 ❌ stf-crc-latest ERROR Project github.com/openstack-k8s-operators/ci-framework does not have the default branch master in 4s |
.zuul.yaml
Outdated
- zuul: github.com/openstack-k8s-operators/ci-framework | ||
# These are the additional repos that zuul will clone | ||
required-projects: | ||
- openstack-k8s-operators/ci-framework |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so you need to do a branch overide here since this uses main
required-projects:
- name: github.com/openstack-k8s-operators/ci-framework
override-checkout: main
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/45e68798954040d9a1ac936718035f53 ❌ stf-crc-latest RETRY_LIMIT in 1m 44s |
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/8746d0848bee4d4c8ba731a9ed50f8c8 ❌ stf-crc-latest ERROR Unable to find playbook /var/lib/zuul/builds/8af33d05d8494bc89747b31ce0460d35/untrusted/project_0/github.com/infrawatch/service-telemetry-operator/ci/post-collectd_logs.yml in 8s |
87d0de3
to
610ec15
Compare
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/43a53a0cbbc844439090636cabbd00a5 ❌ stf-crc-latest RETRY_LIMIT in 2m 41s |
1a0b7e0
to
bf12c6f
Compare
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/0b9c9bb095224a94a19aabc6f409369b ❌ stf-crc-latest FAILURE in 10m 21s |
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/3b850ea52bef42fb8cc13f1c5ed2aea5 ❌ stf-crc-latest FAILURE in 8m 18s |
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/39c9ed754aaa4a039758dc6c4d355915 ❌ stf-crc-latest RETRY_LIMIT in 8m 58s |
check-rdo Rechecking to see if failure is intermittent |
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/5c7f5acb33444917987430d92a54328c ❌ stf-crc-latest FAILURE in 7m 28s |
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/966a1bd1b1b349638b1e95133ac81192 ❌ stf-crc-latest FAILURE in 9m 32s |
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/6ba19130028245dcb371d9b94898ade3 ❌ stf-crc-latest FAILURE in 9m 07s |
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/e87771148cc3446c8979e49a3da4c882 ❌ stf-crc-latest FAILURE in 9m 43s |
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/9ae4a78d9b964d00b82c344f0accd14e ❌ stf-crc-latest FAILURE in 9m 24s |
1cd0bb2
to
6c632fb
Compare
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/00c908e6d28044468e21238ba6dc2ee8 ❌ stf-crc-latest FAILURE in 8m 16s |
6c632fb
to
af04279
Compare
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/61f6f0f2040b4b9b85e642202879bdfc ❌ stf-crc-latest FAILURE in 9m 07s |
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/4861854867484cc7963f00aea2e1390c ❌ stf-crc-latest FAILURE in 9m 20s |
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/fdd5b914f68049778c4fc2db342e15a1 ❌ stf-crc-latest RETRY_LIMIT in 8m 59s |
Build failed (check pipeline). For information on how to proceed, see https://review.rdoproject.org/zuul/buildset/29b2c9d731eb432c97f3960f610414f6 ❌ stf-crc-latest MERGE_CONFLICT in 2s |
Zuul encountered a syntax error while parsing its configuration in the Job stf-crc-latest not defined The error appears in the following job stanza: job: #stf-1.5-ocp-4.10 parent: stf-basedependencies: [make-ocp-4.10]requires:- "ocp-4.10"#stf-1.5-ocp-4.12 parent: stf-base#stf-1.5-ocp-pre-release parent: stf-basein "infrawatch/service-telemetry-operator/.zuul.yaml@master", line 58, column 3 |
recheck |
Zuul encountered a syntax error while parsing its configuration in the Job stf-crc-latest not defined The error appears in the following job stanza: job: #stf-1.5-ocp-4.10 parent: stf-basedependencies: [make-ocp-4.10]requires:- "ocp-4.10"#stf-1.5-ocp-4.12 parent: stf-base#stf-1.5-ocp-pre-release parent: stf-basein "infrawatch/service-telemetry-operator/.zuul.yaml@master", line 58, column 3 |
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/2cb2af4bfdab4eba859c19d22b8adf15 ❌ stf-crc-latest-nightly-bundles RETRY_LIMIT in 8m 40s |
.zuul.yaml
Outdated
# need to set cluster-monitoring | ||
abstract: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No longer true due to latest changes landed on master.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. This PR is going to be wittled down to basically nothing as the other related changes get merged. This one is sticking around to test multiple changes together, so I'm not force pushing to other branches and making it difficult to review
ci/build_stf.yml
Outdated
# TODO: These should be documented at some point | ||
setup_bundle_registry_auth: false | ||
setup_bundle_registry_tls_ca: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If these get added during this PR, then prior to merge the README.md should be updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They got added in one of the changes @vkmc made. README was updated then too.
…es relative to base_dir This will allow configuration of the repo clone destination, so we can use pre-cloned dirs instead of explicitly cloning the dirs each time. This is essential for CI systems like zuul, that set-up the repos with particular versions/branches prior to running the test scripts.
8c9055d
to
2998ac0
Compare
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. |
Using query looks up the kubeconfig on localhost, rather than the host that ansible is executing against. This behaviour is different from either using the shell/command modules or using k8s modules. For consistent behaviour, the queries are replaced with an alternative way to get the same information that will have consistent behahaviour whether executing against localhost or a remote host.
2998ac0
to
a9edd84
Compare
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. |
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. |
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/2ac6c46184a34a6f9ff8876ab38d6cfc ✔️ stf-crc-latest-nightly_bundles SUCCESS in 21m 47s |
This is to avoid wasting resources in the CI; this PR is being kept open to track that the changes made here initially have been merged into master. Once there is no change between this and master, the PR can be closed without merging.
Zuul encountered a syntax error while parsing its configuration in the expected a list for dictionary value @ data['github-check']['jobs'] The error appears in the following project stanza: project: in "infrawatch/service-telemetry-operator/.zuul.yaml@master", line 80, column 3 |
Zuul encountered a syntax error while parsing its configuration in the expected a list for dictionary value @ data['github-check']['jobs'] The error appears in the following project stanza: project: in "infrawatch/service-telemetry-operator/.zuul.yaml@master", line 71, column 3 |
I'm closing this, since most things I added have been merged. The local_build-index_deploy scenario is the last remaining piece, and that is under review at: #495 |
This is a draft/experimenting branch. It will likely not be merged, but will work as a scratchpad for other changes.
Depends-On: infrawatch/smart-gateway-operator#143
For index-deploy scenario:
Depends-On: #470
For local build scenario:
Depends-On: #478