filestore-to-bluestore: reuse dedicated journal (bp #5034) #5094
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
dsavineau
changed the title
dsavineau
force-pushed
the
mergify/bp/stable-4.0/pr-5034
branch
from
cff223a
to
deb42a0
Compare
dsavineau
changed the title
|
jenkins test centos-non_container-filestore_to_bluestore |
|
jenkins test centos-container-filestore_to_bluestore |
|
jenkins test centos-non_container-filestore_to_bluestore |
2 similar comments
|
jenkins test centos-non_container-filestore_to_bluestore |
|
jenkins test centos-non_container-filestore_to_bluestore |
|
jenkins test centos-non_container-filestore_to_bluestore |
1 similar comment
|
jenkins test centos-non_container-filestore_to_bluestore |
dsavineau
changed the title
dsavineau
force-pushed
the
mergify/bp/stable-4.0/pr-5034
branch
from
deb42a0
to
ef8b90e
Compare
dsavineau
changed the title
|
jenkins test centos-non_container-filestore_to_bluestore |
|
jenkins test centos-container-filestore_to_bluestore |
|
jenkins test centos-non_container-filestore_to_bluestore |
1 similar comment
|
jenkins test centos-non_container-filestore_to_bluestore |
If the filestore configuration was using a dedicated journal with either a partition or a LV/VG then we need to reuse this for bluestore DB. When filestore is using a raw devices then we shouldn't destroy everything (data + journal) but only data otherwise the journal partition won't exist anymore. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1790479 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com> (cherry picked from commit 535da53)
dsavineau
changed the title
dsavineau
force-pushed
the
mergify/bp/stable-4.0/pr-5034
branch
from
ef8b90e
to
6ddbe59
Compare
dsavineau
changed the title
|
jenkins test centos-non_container-filestore_to_bluestore |
|
jenkins test centos-container-filestore_to_bluestore |
dsavineau
changed the title
dsavineau
force-pushed
the
mergify/bp/stable-4.0/pr-5034
branch
from
6ddbe59
to
32cf8c2
Compare
dsavineau
changed the title
|
jenkins test centos-non_container-filestore_to_bluestore |
|
jenkins test centos-container-filestore_to_bluestore |
dsavineau
changed the title
We only disable the ceph-osd services but not the ceph-volume lvm services during the filestore to bluestore migration. Signed-off-by: Dimitri Savineau <dsavinea@redhat.com> (cherry picked from commit 38a683e)
dsavineau
force-pushed
the
mergify/bp/stable-4.0/pr-5034
branch
from
32cf8c2
to
739f59f
Compare
dsavineau
changed the title
|
jenkins test centos-non_container-filestore_to_bluestore |
|
jenkins test centos-container-filestore_to_bluestore |
|
jenkins test centos-non_container-filestore_to_bluestore |
|
failure seen here is not specific to this PR (unrelated) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated backport of pull request #5034 done by Mergify.io
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR@Mergifyio backports <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.io/