Enable the ceph-osd@<id> unit during lvm activate to link these
units to the ceph-osd.target.
Signed-off-by: Dan van der Ster <daniel.vanderster@cern.ch>
Fixes: http://tracker.ceph.com/issues/24152
Allow units to be enabled but not persisted across a reboot,
and use this when enabling osds.
Signed-off-by: Dan van der Ster <daniel.vanderster@cern.ch>
Drop unused suites, which ATM means all of them except upgrade/luminous-x
which recently got a cleanup in https://github.com/ceph/ceph/pull/23162
Signed-off-by: Nathan Cutler <ncutler@suse.com>
we could create a mini project to build a shared library, and use
try_compile() to test if the found gperftools is compiled with -fPIC.
but as we are targeting mostly xenial when enabling
WITH_STATIC_LIBSTDCXX, and google-perftools on xenial by default
is built without -fPIC. so let's keep it simple.
Signed-off-by: Kefu Chai <kchai@redhat.com>
- do not link libkv with ALLOC_LIBS, it turns out that if we link
tcmalloc *before* -static-libstdc++ -static-libgcc, libstdc++ and gcc
libs will show up in `ldd` output
- add `-static-libstdc++ -static-libgcc` to CMAKE_SHARED_LINKER_FLAGS
and CMAKE_EXE_LINKER_FLAGS instead of adding them to all shared
libraries and executable. simpler this way.
- link against libtcmalloc statically, because libtcmalloc is a C++
library, linking against it dynamically and linking against C++ runtime
statically will pull in depdencies on two versions of C++ runtime, which
will bring down the app at run-time.
- do not pass '-pie' to linker when building executable if
`WITH_STATIC_LIBSTDCXX` and tcmalloc is used, because the static tcmalloc
is not compiled with PIC.
- only apply '-pie' if ENABLE_SHARED is enabled.
Signed-off-by: Kefu Chai <kchai@redhat.com>
to avoid potential racings on the same shard. before this change, we
apply the change in async. after this change, all changes happens on the
owner shard (i.e. shard.0), and the changes are applied synchronously.
Signed-off-by: Kefu Chai <kchai@redhat.com>
simpler this way, and this allows us to have more detailed error message
so we can present it to end-user. skipping the updating step if no
changes is made is nice to have, but changing settings is not in the
critical path. so let's keep it simple.
Signed-off-by: Kefu Chai <kchai@redhat.com>
before this change, we compare the retcode of _set_val() with 1, and 0,
which are pratically magic numbers. after this change, we use
ConfigValues::set_value_result_t for non-error retcode.
Signed-off-by: Kefu Chai <kchai@redhat.com>
Otherwise the setxattr will fail if the mds has not yet received the MDSMap
which adds the new data pool.
Fixes: https://tracker.ceph.com/issues/25141
Signed-off-by: Patrick Donnelly <pdonnell@redhat.com>
We need to reset the root context of the file system after mounting it.
Otherwise, the SELinux policy rules will not be preserved.
Fixes: https://tracker.ceph.com/issues/24785
Signed-off-by: Boris Ranto <branto@redhat.com>
Duplicate error messages currently appear if the task wrapper service is
used. It calls 'notifyTask' on a failed task, this would be fine if
we didn't have the API interceptor, which watches all API requests and
triggers 'notifyTask' itself if an error appears.
Fixes issue #25139
Signed-off-by: Stephan Müller <smueller@suse.com>
Set a default timeout of 45 seconds to all REST client calls. This can be customized via 'ceph dashboard set-rest-requests-timeout <seconds>'. Currently the REST client is only used by the RGW controller.
Signed-off-by: Volker Theile <vtheile@suse.com>
Latest version of Jest was showing the following error:
"SecurityError: localStorage is not available for opaque origins"
Signed-off-by: Tiago Melo <tmelo@suse.com>
