* refs/pull/68116/head:
ceph-volume: single lvs call to speed up exclude_lvm_osd_devices
ceph-volume: avoid Device() instantiation in lvm OSD filtering
ceph-volume: avoid RuntimeError on ceph-volume raw list with non-existent loop devices
Reviewed-by: Teoman Onay <tonay@ibm.com>
* refs/pull/68451/head:
qa/suites/orch/cephadm: replace "reef" with "v18.2.8"
qa/suites/fs/upgrade/mds_upgrade_sequence: replace "reef" with "v18.2.8"
qa/suites/upgrade: use tagged versions of reef
qa/suites/orch/cephadm: replace "quincy" with "v17.2.8"
qa/suites/fs/upgrade/mds_upgrade_sequence: replace "quincy" with "v17.2.8"
qa/suites/upgrade/telemetry-upgrade: ignore expected health warning
qa/suites/upgrade: use tagged versions of quincy
Reviewed-by: Patrick Donnelly <pdonnell@ibm.com>
Reviewed-by: Yuri Weinstein <yweins@redhat.com>
* refs/pull/68526/head:
qa/tests: v19.2.0 lacks the fix from tracker #66019 which causes NeoRadosCls.RemoteReads
Reviewed-by: Patrick Donnelly <pdonnell@ibm.com>
Reviewed-by: Laura Flores <lflores@redhat.com>
This warning is part of PG_AVAILABILITY, which we already ignore.
The detail message 'pg .* is stuck peering' does not always include
PG_AVAILABILITY explicitly, so add it separately to the ignorelist.
Fixes: https://tracker.ceph.com/issues/69456
Signed-off-by: Yuri Weinstein <yweinste@redhat.com>
to fail during P2P upgrade tests. Bump the starting version to v19.2.1 which
includes the fix. New upgrade path: v19.2.1 -> v19.2.3 -> squid-latest.
Fixes: https://tracker.ceph.com/issues/76030
Signed-off-by: Yuri Weinstein <yweinste@redhat.com>
Since Reef is EOL, the "reef" tag was removed from quay.ceph.io.
The solution is to replace the reef references with the "v18.2.8" tag.
I also added some yaml files to test the reef upgrade path, as those
were missing. These exist in tentacle.
Fixes: https://tracker.ceph.com/issues/76028
Signed-off-by: Laura Flores <lflores@ibm.com>
Since Reef is EOL, the "reef" tag was removed from quay.ceph.io.
The solution is to replace it with a test for the last point release,
which is "v18.2.8".
Fixes: https://tracker.ceph.com/issues/76028
Signed-off-by: Laura Flores <lflores@ibm.com>
We not longer have containers for these HEAD of these branches with the
lab relocation.
This is a direct commit to the squid branch since we got rid of the
reef upgrade path for main/umbrella.
Fixes: https://tracker.ceph.com/issues/76028
Signed-off-by: Laura Flores <lflores@ibm.com>
Since Quincy is EOL, the "quincy" tag was removed from quay.ceph.io.
The solution is to replace the quincy references with the "v17.2.8" tag.
Fixes: https://tracker.ceph.com/issues/76028
Signed-off-by: Laura Flores <lflores@ibm.com>
Since Quincy is EOL, the "quincy" tag was removed from quay.ceph.io.
The solution is to replace it with a test for the last point release
with a container image, which is "v17.2.8".
Fixes: https://tracker.ceph.com/issues/76028
Signed-off-by: Laura Flores <lflores@ibm.com>
"Telemetry requires re-opt-in" briefly shows up when we upgrade.
The test already re-opts in to telemetry to get rid of this warning,
but the cluster badness check still sometimes picks it up.
Fixes: https://tracker.ceph.com/issues/76028
Signed-off-by: Laura Flores <lflores@ibm.com>
We not longer have containers for these HEAD of these branches with the
lab relocation.
We'll use v17.2.8 since v17.2.9 was a limited release without containers.
This is a direct commit to the squid branch since we got rid of the
quincy upgrade path for tentacle and main.
Fixes: https://tracker.ceph.com/issues/76028
Signed-off-by: Laura Flores <lflores@ibm.com>
Prior to c5b43e9b27, we dumped only the
legacy string component from public_addrs as `addr`. Ensure that this
backward compatible filtering is retained when dumping MonMap.
Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
(cherry picked from commit 01c85255bc)
* refs/pull/66541/head:
include: detect corrupt frag from byteswap
mds: dump frag_t as an object
common/frag: produce valid fragments for test instances
common: simplify fragment printing
common: properly convert frag_t to net/store endianness
mds: include sysinfo in status command output
include/frag.h: un-inline methods to reduce header dependencies
Reviewed-by: Yuri Weinstein <yweins@redhat.com>
* refs/pull/67322/head:
qa: set column for insertion
qa: bail sqlite3 on any error
qa: use actual sqlite3 blob instead of string
test: use json_extract instead of awkward json_tree
Reviewed-by: Shraddha Agrawal <shraddhaag@ibm.com>
Under Centos 9 the Java 8 version is recognized by the substring
"java-1.8" rather than "java-8". So the grep has been modified to
accept either.
Signed-off-by: J. Eric Ivancich <ivancich@redhat.com>
(cherry picked from commit a49d4446e4)
Previously s3tests_java.py set JAVA_HOME using the `alternatives`
command. That had issues in that `alternatives` is not present on all
Ubuntu systems, and some installations of Java don't update
alternatives. So instead we look for a "java-8" jvm in /usr/lib/jvm/
and set JAVA_HOME to the first one we find.
Signed-off-by: J. Eric Ivancich <ivancich@redhat.com>
(cherry picked from commit b8e2796270)
* refs/pull/61894/head:
pybind/rados: add note for reversed arguments to WriteOp.zero()
test/pybind/test_rados.py: add test for reversed arguments offset,length in WriteOp.zero
pybind/rados: fix the incorrect order of offset,length in WriteOp.zero
Reviewed-by: Laura Flores <lflores@redhat.com>
Before the fix, zero(0, 2) would have no effect, and read would get '12345' instead of the expected '\x00\x00345'.
Signed-off-by: Wang Chao <sean10reborn@gmail.com>
(cherry picked from commit 3a27c3e58f)
The offset and length parameters in the rados pybind `WriteOp.zero()` method are being passed to the rados_write_op_zero() function in the incorrect order.
Incorrect order cause OP_ZERO not work correctly when use pybind's rados.
Signed-off-by: Wang Chao <sean10reborn@gmail.com>
(cherry picked from commit 049d7d35ab)
* refs/pull/67527/head:
mgr/Mgr.cc: clear daemon health metrics instead of removing down/out osd from daemon state
Reviewed-by: Radoslaw Zarzynski <rzarzyns@redhat.com>
Reviewed-by: Patrick Donnelly <pdonnell@ibm.com>
The following issues with the test are addressed:
1. The test was encountering assertion failure (assert backfillfull < 0.9) with
compression enabled. This was because the condition was not factoring in the
compression ratio. Without it the backfillfull ratio can easily exceed 1. By
factoring in the compression ratio, the backfillfull ratio will be in the
range (0 - n), where n can vary depending on the type of compression used.
2. The main contributing factor for (1) above is the amount of data written to
the pool. The writes were time-bound earlier leading to excess data and
eventually the assertion failure. By limiting the data written to the OSDs
to 50% of the OSD capacity in the first phase and only 20% in the re-write
phase, the outcome of the test is more deterministic regardless of
compression being enabled or not.
3. A potential false cluster error is avoided by swapping the setting of
the nearfull-ratio and backfill-ratio after the re-write phase.
4. Fix a couple of typos - s/tartget/target.
Fixes: https://tracker.ceph.com/issues/71005
Signed-off-by: Sridhar Seshasayee <sridhar.seshasayee@ibm.com>
(cherry picked from commit 91de6a0b7b)
Cache all LVs from one global `lvs` call and use it in
`filter_lvm_osd_devices` to avoid repeated subprocesses and speed up
`ceph-volume generic activate` significantly.
Fixes: https://tracker.ceph.com/issues/74804
Signed-off-by: Guillaume Abrioux <gabrioux@ibm.com>
(cherry picked from commit 56b2250a28)
Replace Device() instantiation with direct LVM API calls to reduce
subprocess overhead.
Use sysfs check first, then only query LVM for actual LVs.
caches LVM mappers list to avoid repeated sysfs reads.
Fixes: https://tracker.ceph.com/issues/74509
Signed-off-by: Guillaume Abrioux <gabrioux@ibm.com>
(cherry picked from commit f247b4e822)
* refs/pull/67884/head:
qa/standalone: shorten bluefs test durations
qa/standalone: increase WAL volume size to 1GB
qa/standalone: fix bluefs expand test case
Reviewed-by: Adam Kupczyk <akupczyk@redhat.com>
* refs/pull/66884/head:
Squid: mgr/dashboard: Changing placement of a mds to label - creates a new mds-service, mds.label
Reviewed-by: Nizamudeen A <nia@redhat.com>
Reviewed-by: Afreen Misbah <afreen@ibm.com>
* refs/pull/62454/head:
mgr/dashboard: add types for mgr-module list
mgr/dashboard: fix access control permissions for roles
Reviewed-by: Afreen Misbah <afreen@ibm.com>
* refs/pull/66838/head:
os/bluestore: rename row names in RocksDBBlueFSVolumeSelector.
test/bluestore: add volume selector tests
os/bluestore:fix bluestore_volume_selection_reserved_factor usage
os/bluestore: print the first RocksDB level which doesn't fit into fast
Reviewed-by: Adam Kupczyk <akupczyk@redhat.com>
