New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kraken: core: ceph-disk: does not support cluster names different than 'ceph' #13497
Conversation
you'll need #13566 as well, as soon as it's merged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please cherry-pick 7f66672 instead
0ce96e3
to
a88b267
Compare
@dachary Please check $ git cherry-pick -x 7f66672
$ git status
$ git diff 16fc6d8 a88b267 src/ceph-disk/ceph_disk/main.py
|
self.create_key() must not be modified at all by the patch. It is part of the context and irrelevant to this commit. |
@dachary Yeah that's perfectly my bad =) Sorry for that. |
Yay finally I'm completely clear about what the title means :) It's taken a long time..., will update.
|
a88b267
to
8ed2e90
Compare
@dachary Please check. Thank you for your patience :)
|
In your file what is right after
|
When dmcrypt is used, the fsid cannot be retrieved from the data partition because it is encrypted. Store the fsid in the lockbox to enable dmcrypt activation using the same logic as regular activation. The fsid is used to retrive the cluster name that was used during prepare, reason why activation does not and must not have a --cluster argument. Fixes: http://tracker.ceph.com/issues/17821 Signed-off-by: Loic Dachary <ldachary@redhat.com> (cherry picked from commit 7f66672) Conflicts: src/ceph-disk/ceph_disk/main.py
8ed2e90
to
6b3655f
Compare
@dachary Oh that's
|
that's better :-) |
@dachary Thanks, very very appreciated!! |
jenkins test this please |
@shinobu-x This commit message is missing a description of how the conflict was resolved. |
@dachary This passed a ceph-disk suite at http://tracker.ceph.com/issues/19009#note-5 OK to merge (note: the commit message is missing a description of how the conflict was resolved)? |
http://tracker.ceph.com/issues/18973