Now, in RGW, if someone want to upload an object using server-side
encryption with providing customer key or kms key id, but not
specify the encryption mode in the
"x-amz-server-side-encryption-customer-algorithm" or
"x-amz-server-side-encryption", the object will be uploaded
successfully without encryption.
This is not a correct way to deal with it. It is better to
return error.
Fixes: http://tracker.ceph.com/issues/21581
Signed-off-by: Enming Zhang <enming.zhang@umcloud.com>
Mark mon_allow_pool_delete as a tracked option. It is always read
from the global conf so users can inject this at runtime.
Signed-off-by: Dan van der Ster <daniel.vanderster@cern.ch>
Merge operators always map to a prefix, just like a CF, so we can link
directly to the operator without doing any lookup.
Signed-off-by: Sage Weil <sage@redhat.com>
- detect and use existing CFs on open
Signed-off-by: Jianjian Huo <jianjian.huo@ssi.samsung.com>
Signed-off-by: Adam C. Emerson <aemerson@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
Validated the label and verified the existence of the label at the beginning of build_branch().
This will avoid:
* Assigning invalid testing labels like 'abcd' and other existing labels like 'bug', 'cleanup' etc; as testing labels
* Stops spamming the Label list in the Ceph repo by creating new (invalid format) labels everytime. The labels can be created manually in github and ptl-tool only uses them.
Signed-off-by: Jos Collin <jcollin@redhat.com>
We were passing this error back to rocksdb, which would then crash (much)
later with a corrupted SST file! No good.
Signed-off-by: Sage Weil <sage@redhat.com>
I'm not quite sure why the FunctionContext did not ever execute on the
finisher thread (perhaps the [&] captured some state on the stack that it
shouldn't have?). In any case, using a traditional Context here appears
to resolve the problem (of the async deferred_try_submit() never executing,
leading to a bluestore stall/deadlock).
Fixes: http://tracker.ceph.com/issues/21470
Signed-off-by: Sage Weil <sage@redhat.com>
We need to wake the kv thread whenever setting deferred_aggressive to
ensure that txns with deferred io that have committed but haven't submitted
their deferred writes get submitted. This aligns us with the other
users of deferred_aggressive (e.g., _osr_drain_all).
Signed-off-by: Sage Weil <sage@redhat.com>
Right now we transparently map a RemoteReservationRejected into a
*Canceled event because this what peers send over the wire. Even
once new peers start sending and explicit CANCEL, old peers will
still do so, so we'll maintain this mapping for a while.
Signed-off-by: Sage Weil <sage@redhat.com>
This reduces pg->reject_reservation() callsites from 2 to 1 and
makes the state transitions a bit more explicit.
Signed-off-by: Sage Weil <sage@redhat.com>
when ./do_cmake.sh add -DWITH_DPDK=ON -DUSE_CRYPTOPP=ON -DWITH_NSS=OFF -DWITH_TESTS=OFF
if build debian package, need remove some file froms install since we disabled TESTS.
Signed-off-by: chunmei <chunmei.liu@intel.com>
The snap_lock is being held when this method is invoked, which can
result in a deadlock.
Fixes: http://tracker.ceph.com/issues/21670
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
