-
Notifications
You must be signed in to change notification settings - Fork 6k
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
ceph-disk: dmcrypt activate must use the same cluster as prepare #13573
Conversation
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>
teuthology-suite -k distro --verbose --suite ceph-disk --ceph wip-17821-revert --machine-type vps pass http://pulpito.ceph.com/loic-2017-02-22_05:31:46-ceph-disk-wip-17821-revert-distro-basic-vps |
teuthology suite for ceph-disk passes #13573 (comment) |
There are no specific tests for this change. But it modifies the code path used by every dmcrypt activation and I believe that's enough coverage, via the teuthology ceph-disk suite, to prove it does the right thing. |
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.
since the problem attacked by #11786 is a false problem, we should revert it.
@leseb the backport is in progress at #13496 . It looks like Loic has requested changes of the reviewer. If this needs to get into v10.2.7, please work with @shinobu-x on that. At this point in the schedule anything for v10.2.7 must have Pulpito links to successful Teuthology runs demonstrating that the change is safe to take in. |
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