Set the v1.1.5 release tag

With the v1.1.5 release we update the manifests with the new tag.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

ceph: fix set mgr annotations (bp #4195)

Mgr annotation was previously not being set.
Signed-off-by: d-luu <david@davidluu.info>
(cherry picked from commit 014431ee)

ceph: added a check for triggering the orchestration (bp #4252)

Fix for automatic orchestration triggering even if the cluster CRD is unchanged.
Signed-off-by: Nizamudeen <nia@redhat.com>
(cherry picked from commit 1aaad8f3)

ceph: helm: fix operator chart rbdGrpcMetricsPort (bp #4202)

Added missing csi values of the Rook Ceph operator helm chart to the
documentation.
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
(cherry picked from commit 020626a4)

This fixes the conditional for the `rbdGrpcMetricsPort` option.
Previously the `rbdGrpcMetricsPort` was useless as it was not used,
instead the Helm chart looked for `cephfsrbdGrpcMetricsPort` option.
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
(cherry picked from commit 9fe5e2ad)

Build Fix: Update the path to pull the yq tool (bp #4240)

The yq tool changed and requires a new path from which to build.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit d79c8a61)

Support all layers of CRUSH map with node labels (bp #4236)

Clean up block integration tests more reliably (bp #4217)

The node labels were already supported for zones and regions to add to
the CRUSH map. Now all layers of the CRUSH map will be supported
with the new labels such as topology.rook.io/rack.
The labels will be detected at the osd startup time
similar to the zone and region labels already being detected.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit 831c1508)

The block integration tests are a source of intermittent failures
in the CI. The PVCs were not being confirmed as removed before the
pools were deleted. Then the pool would not be removed since there
might still be a block image from the PVC that wasn't deleted yet.
Now the tests will ensure the PVCs and their block images are
removed before the pool is deleted.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit e3272926)

stop orchestration restart on device config map update for osd on pvc (bp #4222)

Ceph: fix the deduplication of tolerations collected for the drain-canary (bp #4220)

ceph: Included missing rolebindings for PSP in Helm chart (bp #4224)

**Description of your changes:**
Include missing rollebindings present in common.yaml file and not in the
rolebindings file for the Ceph Helm chart.

Resolves #
Signed-off-by: Juan Miguel Olmo Martínez <jolmomar@redhat.com>
(cherry picked from commit 9c152e74)

- Implement exportable TolerationSet with the following differences:
  - Change map key to a string to ensure it is deterministic.
    The old key was a struct that included a pointer.
  - Sort the outputted list by this key to ensure the order is deterministic.
  - Get the tolerations from the deployment instead of the pod as pod tolerations
    are sometimes modified by the system. We only want user provided tolerations
    in our deployment.
- Modify tests to try duplicate keys from different structs. The old way tested duplicate
  keys using the same structs.
Signed-off-by: Rohan CJ <rohantmp@gmail.com>
(cherry picked from commit b16d55f4)

when running OSD on PVC, orchestration should not be started again if there is any change in the device config
map. Added a check to skip orchestration on device CM update when StorageClassDeviceSets are available,
that is, when running osd on pvc.
Signed-off-by: Santosh Pillai <sapillai@redhat.com>
(cherry picked from commit d1c82015)

Continue with orchestration if a single mon pod fails to start (bp #4216)

ceph: osd hide 'restorecon' when necessary (bp #4214)

Some testing on OpenShift has shown that enabling Hostnetworking causes
issues with ceph-volume creating OSD.
This is a pure Red Hat OpenShift downstream issue.

This is meant to be temporary while we are waiting for the Selinux team
to get back to us.
Signed-off-by: Sébastien Han <seb@redhat.com>
(cherry picked from commit d224fbde)

If the cluster has previously been initialized and the operator
is restarted, the operator needs to perform the first orchestration
to confirm basic cluster health, then start watching for CR events.
If there was a single mon pod in a failed or pending pod state, the
orchestration was blocked even if just one mon was in this state.

The scenario is when a node is lost and a mon and the operator happen
to be running on that node. The operator will restart, but the mon
will not restart because it is tied to the node that died (unless running
on a PVC). The mon would remain in a pending state while attempting
to schedule on the node that is down indefinitely and the operator would
be blocked indefinitely. Now we will just log the error and attempt
to continue.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit 95171c68)

Add a more meaninful message.
Signed-off-by: Sébastien Han <seb@redhat.com>
(cherry picked from commit 6dff2afe)

Ceph: use the rook image for drain-canaries. (bp #4213)

Change the canaries to use the rook image instead of the busybox image to
run `sleep infinity`. This removes our dependency on an external image that
we do not control.
Signed-off-by: Rohan CJ <rohantmp@gmail.com>
(cherry picked from commit 17f6a25b)

NFS: Set correct owner reference for garbage collection (bp #4179)

ceph: fix set osd prepare resources (bp #4189)

Run the distributed test matrix in PRs (bp #4096)

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>
(cherry picked from commit ac8f0dff)

Flex driver should not allow attach before detach on a different node (bp #4180)

Use the right struct field. Previously it was pointing to the osd global
resource now it does the osd prepare.

Closes: https://github.com/rook/rook/issues/4182

Signed-off-by: Sébastien Han <seb@redhat.com>
(cherry picked from commit 56629113)

Improve reliability of the Ceph mon failover test (bp #4184)

The owner reference for the NFS custom resource was using the namespace
instead of the name. This causes the k8s garbage collector to remove the
nfs resources in some scenarios such as restarting etcd.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit fa834d9a)

Depending on the state of the orchestration, the operator might trigger
re-creation of the deleted mon. In this case, consider the test successful
rather than wait for the failover which will never occur.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit f5b032ad)

If a volume is being attached, it should be verified that the volume
is safe to attach. The volume was assumed to be safe to attach if it was
for the same pod. But this was assuming the pod of the same name would be
on the same node. This is true for pods created from deployments, but not
for pods that are part of a stateful set. A stateful set will maintain the
pod name even as the pod is failed over to a new node. Therefore, the fencing
much check if the pod is from the same node before allowing the attach to
continue. Otherwise, we need to wait for the volume to be detached from the
other node.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit f7d7aa0b)

Set the v1.1.4 release tag

With the v1.1.4 patch release we need to set the new tag in the
deployment manifests and documentation.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>