Closed rzetelskik closed 4 months ago
@rzetelskik: GitHub didn't allow me to request PR reviews from the following users: rzetelskik.
Note that only scylladb members and repo collaborators can review this PR, and authors cannot review their own PRs.
/cc zimnx tnozicka
https://github.com/scylladb/scylla-operator/issues/1525#issuecomment-2049733594
https://github.com/scylladb/scylla-operator/issues/1694#issuecomment-2049735439
I don't see how these changes could contribute to flakiness, since it's just some changes in machinery, so I'm not investigating.
/test images /retest
@rzetelskik: The following test failed, say
/retest
to rerun all failed tests or/retest-required
to rerun all mandatory failed tests:Test name Commit Details Required Rerun command ci/prow/e2e-gke-parallel 9ff84af link true
/test e2e-gke-parallel
Full PR test history. Your PR dashboard.
Cluster provisioning failed. /test images /retest
@rzetelskik: The following test failed, say
/retest
to rerun all failed tests or/retest-required
to rerun all mandatory failed tests:Test name Commit Details Required Rerun command ci/prow/e2e-gke-serial 61326f2 link true
/test e2e-gke-serial
Full PR test history. Your PR dashboard.
Cluster provisioning failed. /retest
@rzetelskik: The following test failed, say
/retest
to rerun all failed tests or/retest-required
to rerun all mandatory failed tests:Test name Commit Details Required Rerun command ci/prow/e2e-gke-parallel-clusterip d3b46ef link true
/test e2e-gke-parallel-clusterip
Full PR test history. Your PR dashboard.
Known Scylla Manager flake. Already working on it, this PR is unrelated.
/retest
@zimnx thanks for the review, I replied to all of your comments
@rzetelskik: The following tests failed, say
/retest
to rerun all failed tests or/retest-required
to rerun all mandatory failed tests:Test name Commit Details Required Rerun command ci/prow/e2e-gke-parallel 66167d5 link true
/test e2e-gke-parallel
ci/prow/e2e-gke-parallel-clusterip 66167d5 link true/test e2e-gke-parallel-clusterip
Full PR test history. Your PR dashboard.
known manager flake for both, not investigating since it's unrelated and we're already working on fixing it /retest
/hold for https://github.com/scylladb/scylla-operator/pull/1901 to rebase
/hold cancel
I'll test the changes against a multi-datacenter e2e after we'll have gone through all review iterations, I takes too long to do this every time /hold
lgtm, but you need to fix the CI failure
https://github.com/scylladb/scylla-operator-release/pull/206 sent a PR to fix the typo on the CI side
https://github.com/scylladb/scylla-operator-release/pull/206 landed /retest
/lgtm
Waiting for cluster to be provisioned...
Cluster provisioning failed. Exiting.
Missing kubeconfigs.
Usage: /usr/bin/bash kubeconfig [kubeconfig ...]
@rzetelskik: The following test failed, say
/retest
to rerun all failed tests or/retest-required
to rerun all mandatory failed tests:Test name Commit Details Required Rerun command ci/prow/e2e-gke-release-script-latest d03fb8e link unknown
/test e2e-gke-release-script-latest
Full PR test history. Your PR dashboard.
Waiting for cluster to be provisioned...
Cluster provisioning failed. Exiting.
Missing kubeconfigs.
Usage: /usr/bin/bash kubeconfig [kubeconfig ...]
@tnozicka should I fix this in scylla-operator-release (pass kubeconfig to funcs) or make them discover kubeconfigs here?
I'd use the env vars for KUBECONFIGS
to match how everything else handles KUBECONFIG
. If you get KUBECONFIGS
it wins over a KUBECONFIG
, if you get KUBECONFIG
, translate it to KUBECONFIGS[0]
so you can use KUBECONFIGS
consistently, if needed.
I'd use the env vars for KUBECONFIGS to match how everything else handles KUBECONFIG. If you get KUBECONFIGS it wins over a KUBECONFIG, if you get KUBECONFIG, translate it to KUBECONFIGS[0] so you can use KUBECONFIGS consistently, if needed.
You can't really pass/test arrays as env vars that way, so best I could do here is to do this for KUBECONFIG_DIR
on sourcing e2e lib. Unless you know a reasonable workaround for this.
You can't really pass/test arrays as env vars that way, so best I could do here is to do this for KUBECONFIG_DIR on sourcing e2e lib.
sounds good
You can't really pass/test arrays as env vars that way, so best I could do here is to do this for KUBECONFIG_DIR on sourcing e2e lib. sounds good
ok, done
@tnozicka I realised I haven't passed kubeconfigs to the e2e pod in this PR. Should we land this as a starting point regardless? As I'm trying to run a multi-dc e2e test I'll probably bump into some other issues, but I think the baseline for framework etc is solid.
I am fine with followups
/approve /lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rzetelskik, tnozicka, zimnx
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/hold cancel
Description of your changes: This PR adds support for multi-datacenter clusters in our test runner and scripts.
Which issue is resolved by this Pull Request: Prerequisite for https://github.com/scylladb/scylla-operator/pull/1632.
/kind feature /priority important-longterm /cc