moving the toolbox-operator creation early in
ci, so that by the time we wait for others pods
to come up, toolbox-operator will be ready or
will wait for 180s.
Signed-off-by: subhamkrai <srai@redhat.com>
While running object test we need some more time
to run the cosi test completely so increasing the timeout
Also update timeout of ntegration-tests-on-release.yaml
Signed-off-by: parth-gr <paarora@redhat.com>
add a new toolbox yaml manifest which will use the
rook image instead of ceph image
for running s5 cmd container needs to run with rook image
closes: https://github.com/rook/rook/issues/12227
Signed-off-by: parth-gr <paarora@redhat.com>
recentally, upgrade tests are getting
longer than 30m to pass since reef upgrade.
So, increasing the timeout to 40m.
Signed-off-by: subhamkrai <srai@redhat.com>
The build and release actions will rarely ever need to be
debugged. To make them more efficient and reduce their
runtime, we remove the tmate action so it won't add 10
unnecessary minutes to the end of the action.
Signed-off-by: travisn <tnielsen@redhat.com>
The object suite was being skipped in master and release
branches. Since the object suite was only running in PRs
it was not noticed if there were any issues in the master
branch or release branches. Now we run it in these branches
in addition to the PRs.
Signed-off-by: travisn <tnielsen@redhat.com>
The previous client loader routine assumed KUBECONFIG would be set in
CLI environments. Instead, now take this approach:
1. If KUBECONFIG is set, that is the de-facto override that informs the
tool it is being run in a CLI environment.
2. Otherwise, try creating a client from the default kube config file.
3. If that fails, assume the tool is running in a Kubernetes Pod.
This will continue supporting dev/test environments so that building the
rook container is not necessary for development. It also allows support
for highly opinionated environments (like deployed by OpenShift CSVs)
where it's not possible to install the Rook operator without also
deploying a CephCluster.
Signed-off-by: Blaine Gardner <blaine.gardner@ibm.com>
the upgrade suite for version 1.27.x is failing
due
```
debug 2023-07-24T19:11:20.264+0000 7f3395a82c80 -1 error: monitor data filesystem reached concerning levels of available storage space (available: 5% 4.4 GiB)
you may adjust 'mon data avail crit' to a lower value to make this go away (default: 5%)
```
so adding mon setting to start on `compact` also adding
other setting present in cluster-test.yaml.
Signed-off-by: subhamkrai <srai@redhat.com>
with detached mode, we don't need to wait for the
tests to complete. Now, we can get inside tmate before
the tests start and we can monitor the tests.
By default, this mode will wait at the end of the job for
a user to connect and then to terminate the tmate session.
If no user has connected within 10 minutes after the post-job step started,
it will terminate the tmate session and quit gracefully.
Signed-off-by: subhamkrai <srai@redhat.com>
set the csi subvolume to pin type distributed and pin setting 1
So to statically balance the PVs across all MDS ranks
Signed-off-by: parth-gr <paarora@redhat.com>
we need make `limit-access-to-actor: false` and also
in the right place where tmate `uses` is called for
composite yaml.
Signed-off-by: subhamkrai <srai@redhat.com>
we need to wait for the rgw pod to be delete and not
only the cephobjectsore, sometime the pod could be in
terminating state. Also, in some place it require proper
command to wait for pod to be ready/delete and get the
pod name only.
Signed-off-by: subhamkrai <srai@redhat.com>
For v1.12 update the minimum K8s version supported to v1.22,
and run CI against the most recent six versions.
Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>
The linter requires updating wait.Poll methods to more recent
given the new dependencies for the controller runtime.
Signed-off-by: travisn <tnielsen@redhat.com>
Currently, if there is any change in the API we need to separately
run the make generate-crd-docs but with this change
make crds will also update the generated docs
Also improved the file locations
Closes: https://github.com/rook/rook/issues/12310
Signed-off-by: parth-gr <paarora@redhat.com>
there is error in the script to check if there
is any changes on go.mod or go.sum line.
```
/home/runner/work/_temp/dc877811-e494-4d57-ab19-a37942eac23d.sh: line 1: unexpected EOF while looking for matching `)'
```
instead of this `if [[ $(git status | grep -E '(go.mod|go.sum)' ]]; then` it will be
`if [[ $(git status | grep -E '(go.mod|go.sum)') ]]; then`
Signed-off-by: subhamkrai <srai@redhat.com>
IMO, earlier we're triggering the dependabot in wrong
branches `"dependabot/bundler**"` instead it should be
`"dependabot/go_modules/**"` since it create branches with
the above syntax.
For example:
dependabot/go_modules/golang.org/x/sync-0.2.0
Fixes: #12352
Signed-off-by: subhamkrai <srai@redhat.com>
The daily rgw tests were mistakenly running against an old
latest-master-devel ceph tag instead of the newer
latest-main-devel ceph tag. Now the daily rgw tests will
be run against the latest and greatest as expected.
Signed-off-by: travisn <tnielsen@redhat.com>
currently we just print the error is anything fails in
script for rgw, So by that there is no panic or
failiure of script if something wrong happened,
Added Explicittly forcing to catch the error from
the error message that is thrown
Closes: https://github.com/rook/rook/issues/12244
Signed-off-by: parth-gr <paarora@redhat.com>
The main objective of this commit is to stop CI to run tests when only documentations are changed. We did that by adding the Documentation and design folder into paths-ignore key on CI files.
Signed-off-by: Gabriel Morishita <gabrielmorishita@hotmail.com>
Add a CI e2e test for the multus validation routine that runs whenever
the multus validation test is modified and on master/releases.
Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
subhamkrai
Travis Nielsen
parth-gr
Blaine Gardner
Nikhil-Ladha
dependabot[bot]
Javier
Sheetal Pamecha
Blaine Gardner
Gabriel Morishita
Satoru Takeuchi