Closed matofeder closed 2 months ago
Build canceled (e2e-quick-test pipeline).
Hi @jschoone, it should be possible now to trigger the pipeline by adding the label e2e-quick-test
for e2e-openstack-quick
tests or e2e-test
for e2e-openstack-conformance
tests like it is in k8s-cluster-api-provider
repo.
Hi @jschoone, it should be possible now to trigger the pipeline by adding the label
e2e-quick-test
fore2e-openstack-quick
tests ore2e-test
fore2e-openstack-conformance
tests like it is ink8s-cluster-api-provider
repo.
Thanks @michal-gubricky, will try it tomorrow :)
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/46f4121ef60c437f9c79e226c5c4f0c3
:x: e2e-openstack-quick FAILURE in 10m 06s
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/09635b26ad744a23976c2e1ea917302c
:x: e2e-openstack-quick FAILURE in 22m 31s
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/e3fd00d93be042cd91da30828817c597
:x: e2e-openstack-quick RETRY_LIMIT in 12m 05s
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/e3fd00d93be042cd91da30828817c597
❌ e2e-openstack-quick RETRY_LIMIT in 12m 05s
Failed during building a csctl
, problem is the last commit in this repository. Take a look at https://github.com/SovereignCloudStack/csctl/actions/runs/9205776982/job/25322184680
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/dff267a37d094645a03daa2459272c09
:x: e2e-openstack-quick FAILURE in 18m 35s
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/429f228537224c1086e165363ac32658
:x: e2e-openstack-quick FAILURE in 30m 26s
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/429f228537224c1086e165363ac32658
❌ e2e-openstack-quick FAILURE in 30m 26s
Failed during sonobuoy tests with error: failed to get namespace sonobuoy: etcdserver: request timed out and etcdserver: leader changed
, check logs.
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/e432bfc2e63c443eb20be0d93611a197
:x: e2e-openstack-quick FAILURE in 21m 19s
Build succeeded (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/2107ac4c1c684914a2f9927ff5ed926f
:heavy_check_mark: e2e-openstack-quick SUCCESS in 30m 05s
Warning:
Hi @michal-gubricky, can the playbooks
dir moved into .zuul
to ensure the context in which they are placed?
Hi @michal-gubricky, can the
playbooks
dir moved into.zuul
to ensure the context in which they are placed?
Hi, I think it is a common pattern to have .zuul.yaml
in a <project-root>
and also have the playbooks
dir there, where are placed ansible playbooks/tasks which are used in zuul pipeline. For example, we use this structure in k8s-cluster-api-provider also other organizations use this structure like OSISM
. But surely we can discuss it more here.
Hi @michal-gubricky, can the
playbooks
dir moved into.zuul
to ensure the context in which they are placed?Hi, I think it is a common pattern to have
.zuul.yaml
in a<project-root>
and also have theplaybooks
dir there, where are placed ansible playbooks/tasks which are used in zuul pipeline. For example, we use this structure in k8s-cluster-api-provider also other organizations use this structure likeOSISM
. But surely we can discuss it more here.
I see, thanks for checking
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/a9920c1654fb4cd5bef434333563e03a
:x: e2e-openstack-quick FAILURE in 17m 53s
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/4176272e3cf34c23a407681c256522fd
:x: e2e-openstack-quick FAILURE in 21m 50s
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/3d0d701a0c854170bdb182801c3d8334
:x: e2e-openstack-quick FAILURE in 17m 42s
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/e204643f706249629b171a75e61a39c6
:x: e2e-openstack-quick FAILURE in 35m 19s
Warning:
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/4263beb456634b00a1c6128383a54e0a
:x: e2e-openstack-quick FAILURE in 21m 12s
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/2e2fad872bc34eda8c12f0115dd86bd0
:x: e2e-openstack-quick FAILURE in 31m 53s
Warning:
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/5768cfb441a648678dcd0fe2cfe6914d
:x: e2e-openstack-quick FAILURE in 37m 02s
Warning:
Build canceled (e2e-quick-test pipeline).
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/d5e1188c39114699abb88c56ccd19718
:x: e2e-openstack-quick FAILURE in 41m 40s
Warning:
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/9f4c798e9d6f4b658e1586732a75f3d6
:x: e2e-openstack-quick FAILURE in 18m 34s
Build failed (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/034bc20af19e42abb1f5be6611f39373
:x: e2e-openstack-quick FAILURE in 22m 36s
Build canceled (e2e-quick-test pipeline).
Build canceled (e2e-quick-test pipeline).
Build succeeded (e2e-quick-test pipeline). https://zuul.scs.community/t/SCS/buildset/9b1cd326c0f54257abaee4fd09b68e14
:heavy_check_mark: e2e-openstack-quick SUCCESS in 38m 39s
Warning:
Closes https://github.com/SovereignCloudStack/cluster-stacks/issues/31
The
cluster_stack
you want to test with this e2e pipeline must be specified viazuul_config
in the description of the PR, like it is done here, otherwise it will testopenstack-alpha-1-29
, which is currently as a default.The Zuul pipeline cannot be triggered by the label until this PR is merged.
For more details, check this doc