The go modules are changed by the install of the junit
tool for the unit tests. Before the release build we need
to ensure that the modules are tidied.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

The CI is using an older version of git that doesn't
recognize git restore.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

The master build is publishing with the dirty tag so we
need to ensure that the files do not remain modified.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

With the release of k8s 1.18 we now will run the integration
tests on 1.14 through 1.18 in master.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

The recent change to go modules is causing a file to change
during the build, which results in a dirty tag to be
generated.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

Every developer should commit all the files that need to be changed
in a given set of changes. The go.sum file was not being generated
as expected since the update to go modules. Since the Jenkinsfile
was running make mod.check, the build was ending up with a modified
file, which caused a dirty tag on the build. Now it is expected
that each PR will merge with the corresponding go.sum changes.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

This switches to use `go.mod.check` target instead of `go.vendor.check` target.
Signed-off-by: moricho <ikeda.morito@gmail.com>

This switches Rook to use `go mod` instead of `dep` for
dependencies management.
Signed-off-by: moricho <ikeda.morito@gmail.com>

This commit updates the jenkins file to pre clean the k8s cluster before the running the integeration tests.
Signed-off-by: Ashish Ranjan <aranjan@redhat.com>

This commit updates jenkins file for executing localPathPV.sh during
bootstrapping of k8s cluster. The localPathPV.sh script is responsible
for creating localPathPVs over disks in the nodes.
Signed-off-by: Ashish Ranjan <ashishranjan738@gmail.com>

The CI will now use the current latest K8S releases.
v1.15: v1.15.9
v1.16: v1.16.6
v1.17: v1.17.2
Signed-off-by: Alexander Trost <galexrt@googlemail.com>

Checking that the flex driver tests succeed on 1.17.1 as well
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

With the release of K8s 1.17 Rook needs to test on this new version.
The integration tests will now run the tests across K8s 1.13-1.17.
The pattern has been to run the tests across the most recent five
versions.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

The version suffix such as alpha.0, beta.0, or rc.0 only apply
when running the tag pipeline or the release build. Otherwise,
we don't want to use the suffix from the master build.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

Using the current working directory as the base test directory
fails with an unclear error message when running mkfs for OSDs
if tests are run when the k8s master node is not running on
localhost.

This change creates a new flag for the test suite to set the
base test directory, but uses a default that is safe for
virtualized test environments ("/data").

Fixes: #4205
Signed-off-by: egafford <egafford@redhat.com>

With the desire to run the integration tests on the five
most recent versions of K8s, 1.16 is added and 1.11
is removed from the integration test matrix.
Signed-off-by: travisn <tnielsen@redhat.com>

The CI runs the integration tests on several versions of K8s. By default
the integration tests have all been running on all versions of K8s. With the
recent option to run a minimum matrix for ceph tests it has shown to be reliable
for PRs and is much faster to have the test distribution.

Master and release builds will still run the full set of test suites on all
versions of K8s.
Signed-off-by: travisn <tnielsen@redhat.com>

There are six test suites and six k8s versions where we currently run
the tests. For efficiency we can restrict the testing to one suite
per k8s version. Bigger or riskier changes should still run the full
set of suites on all versions. To trigger the smaller test matrix, add
[test ceph min] to the PR description
Signed-off-by: travisn <tnielsen@redhat.com>

Signed-off-by: Sameer Kulkarni <samkulkarni20@gmail.com>

The integration tests for storage providers will be skipped
for example if [test ceph] is specified. If the [test] tag
is not specified, all tests should be run. If the tag is not
specified, the Jenkinsfile will pass null, which needs to be
handled by the test code deciding to run all the tests.
Signed-off-by: travisn <tnielsen@redhat.com>

If no storage provider is found, let's assign env.testProvider with an
empty string so that we wil run all the tests.
Signed-off-by: Sébastien Han <seb@redhat.com>

Since most PRs are focused on a single storage provider,
the tests for other storage providers do not need to be
run. The CI will allow skipping tests for other storage
providers by specifying keywords in the PR description.
Similar to [skip ci], you can now specify [test storage-provider].
For example, [test ceph] will only trigger the test
suites for ceph and none of the other storage providers.
Signed-off-by: travisn <tnielsen@redhat.com>

Signed-off-by: travisn <tnielsen@redhat.com>

Signed-off-by: Santosh Pillai <sapillai@redhat.com>

Signed-off-by: travisn <tnielsen@redhat.com>

The master build will be published as soon as the basic build and unit tests
are completed. This ensures that the generated help documentation matches
what is in master and the latest master published build matches
the yaml files in master. The longer the delay between merging and
publishing, the more likely users are to run into issues with
test deployments. This change minimizes the gap.
Signed-off-by: travisn <tnielsen@redhat.com>

Signed-off-by: travisn <tnielsen@redhat.com>

Simple integration test for Cassandra.
Boilerplate in setup scripts for Jenkins.
Signed-off-by: Yannis Zarkadas <yanniszarkadas@gmail.com>

Introduce mount security mode for basic multi tenancy

Fixes #2164.

This adds three new parameters/options to StorageClass/flexvolume entry:
* `mountUser`
* `mountSecret`
* `mountSecretNamespace`
Signed-off-by: Alexander Trost <galexrt@googlemail.com>

Signed-off-by: mickymiek <meunie_m@etna-alternance.net>

this commit updates dep to version 0.5, and adds a check during
CI runs that enforces that the vendor dependencies have not changed.
There is a now a makefile target `make vendor.check` that performs
this check. Also removed the requirement that PR run make vendor as
this will be done by CI.
Signed-off-by: Bassam Tabbara <bassam@upbound.io>

Resolves #981
Signed-off-by: Alexander Trost <galexrt@googlemail.com>

This is a temporary patch to help us figure out what is causing the random
issues on concurrent builds and re-using an instance.

This patch also makes the log names concise and consistent across all versions.
Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>

Signed-off-by: Ratnadeep Debnath <rtnpro@gmail.com>

Signed-off-by: rohan47 <rohanrgupta1996@gmail.com>

Signed-off-by: Jared Watts <jbw976@gmail.com>

Signed-off-by: travisn <tnielsen@redhat.com>

Signed-off-by: travisn <tnielsen@redhat.com>

Signed-off-by: travisn <tnielsen@redhat.com>

prepare osd in a job per node. Once all osds are prepared, store osd info in orchestration configmap.
Operator watches the configmap, starts one osd replica set per osd.
Signed-off-by: Huamin Chen <hchen@redhat.com>