General

Profile

Or Ozeri

  • Registered on: 04/20/2021
  • Last connection: 02/13/2022

Issues

Projects

Activity

01/06/2022

12:46 PM rbd Bug #53786 (New): rbd diff crashes on a migrating image
reproduce steps:
- prepare migrate from raw format
- run rbd diff on the migrating image
ceph assertion fails:
...

12/20/2021

02:34 PM rbd Bug #53674 (Fix Under Review): Reading from an image being live-migrated from an encrypted export...
Consider the following use-case, with the following sequence of user operations:
1. user creates an RBD image
2. ...

12/13/2021

08:54 AM rbd Cleanup #53592 (New): qa/tasks/qemu - use librbd encryption directly via qemu
qa/tasks/qemu currently sets-up an NBD device when testing with encrypted rbd images.
This is a temporary workaround...

12/12/2021

02:40 PM rbd Bug #53587 (Resolved): Failure in qemu_xfstests_luks{1,2} on centos 8.stream
These tests currently pass on all distros, except for centos 8.stream.
See here:
https://pulpito.ceph.com/trociny-2...

12/01/2021

12:43 PM sepia Support #53447: Sepia Lab Access Request
orozery gmail com
Thanks!
07:41 AM sepia Support #53447 (Resolved): Sepia Lab Access Request
1) Do you just need VPN access or will you also be running teuthology jobs?
VPN + access to schedule jobs (and view ...

11/28/2021

11:50 AM rbd Bug #53417: librbd/crypto: Uninitialized image data may be gibberish
To reproduce, you may need to read from an area where the relevant rados object exists, so first write a small amount...
11:21 AM rbd Bug #53417 (Fix Under Review): librbd/crypto: Uninitialized image data may be gibberish
By convention, librbd returns zeros when reading uninitialized image data.
When using encryption, this convention is...

11/25/2021

09:34 AM rbd Bug #49876: [luks] sporadic failure in TestLibRBD.TestEncryptionLUKS2
I reproduced this issue with debug enabled on pwl as well.
Looks like that pwl is flushing both writes concurrently,...

11/16/2021

06:29 AM rbd Bug #49876: [luks] sporadic failure in TestLibRBD.TestEncryptionLUKS2
@Deepika The two writes at the end of the test should not race, but rather the second write is expected to begin only...

Also available in: Atom