kraken: rbd: Add missing parameter feedback to 'rbd snap limit' #14537
Conversation
Signed-off-by: Tang Jin <tang.jin@istuary.com> (cherry picked from commit 8860028)
|
@joscollin Yes, that's intentional. Allow me to explain. This is a backport - i.e. a cherry-pick. When backporting, we intentionally keep the original commit message as it is, adding information only to explain differences introduced by the backporting process (i.e. conflict resolution). The advantage is that it is clear at first glance that this is a clean cherry-pick: nothing was changed. The tracker may be missing in the master commit, but if we "fix" that we introduce doubt concerning whether the cherry-pick is really clean. |
|
@smithfarm Thanks for the explanation. |
|
@dillaman This passed an rbd suite at http://tracker.ceph.com/issues/19009#note-29 There are some failures in the upgrade/jewel-x and upgrade/client-upgrade suites, but the only unexplained one is http://tracker.ceph.com/issues/19637 OK to merge under those conditions? |
http://tracker.ceph.com/issues/18601