Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1477775 - ceph-disk: dm-crypt breaks after upgrade to RHCS 2.3
ceph-disk: dm-crypt breaks after upgrade to RHCS 2.3
Status: CLOSED ERRATA
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: Ceph-Disk (Show other bugs)
2.3
Unspecified Unspecified
urgent Severity urgent
: rc
: 2.4
Assigned To: Loic Dachary
Vasishta
Bara Ancincova
:
Depends On:
Blocks: 1439210 1479701
  Show dependency tree / graph
 
Reported: 2017-08-02 18:19 EDT by Alexandre Marangone
Modified: 2017-09-05 16:49 EDT (History)
8 users (show)

See Also:
Fixed In Version: RHEL: ceph-10.2.7-32.el7cp Ubuntu: ceph_10.2.7-33redhat1
Doc Type: Bug Fix
Doc Text:
.Encrypted OSDs no longer fail after upgrading to 2.3 Since version 2.3, a test has been added that checks if the `ceph_fsid` file exists inside the `lockbox` directory. If the file does not exist, an attempt to start encrypted OSDs fails. Because previous versions did not include this test, after upgrading to 2.3, the encrypted OSDs failed to start after rebooting. This bug has been fixed, and encrypted OSDs no longer fail after upgrading to version 2.3 or later.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-09-05 16:49:52 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
icolle: needinfo+
icolle: needinfo+

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Ceph Project Bug Tracker 20893 None None None 2017-08-03 04:53 EDT
Red Hat Product Errata RHBA-2017:2640 normal SHIPPED_LIVE Red Hat Ceph Storage 2.4 bug fix and enhancement update 2017-10-10 16:18:35 EDT

  None (edit)
Description Alexandre Marangone 2017-08-02 18:19:25 EDT 
Description of problem:
2.3 added a piece a of code to check for a ceph_fsid file inside the lockbox directory of a dm-crypt OSD. If that ceph_fsid file doesn't exist, it exists and fails.

2.2 did not have that piece of code. After an upgrade to 2.3, rebooting a node will not remap the OSDs. Manually creation the ceph_fsid on each lockbox is the only way to get them up and running.
Comment 2 Ian Colle 2017-08-02 18:47:58 EDT 
Need a quick patch to 2.y, so moving from 3.0.
Comment 3 Loic Dachary 2017-08-03 04:50:05 EDT 
A quick fix would be to instruct the sysadmin to manually create the ceph_fsid file.
Comment 4 Loic Dachary 2017-08-03 05:00:51 EDT 
https://github.com/ceph/ceph/pull/16776 is the proper fix, testing it now
Comment 5 Ian Colle 2017-08-07 09:55:14 EDT 
https://github.com/ceph/ceph/pull/16859 Is Jewel backport
Comment 6 Ian Colle 2017-08-07 10:31:31 EDT 
Correction to above: https://github.com/ceph/ceph/pull/16870 is correct PR.
Comment 12 Loic Dachary 2017-08-22 16:07:04 EDT 
The description is perfect :-)
Comment 19 Loic Dachary 2017-08-29 04:49:35 EDT 
This is great news. The text looks good to me !
Comment 22 Vasishta 2017-08-30 09:19:27 EDT 
Hi,

We worked on upgrading cluster from 2.2 to 2.4 both on RHEL and Ubuntu, having OSDs with both collocated and dedicated journals and It worked fine.

We executed some smoke tests like rolling reboot of OSD nodes, service restarts after the upgrade  It worked as expected.

Moving the BZ to VERIFIED state.

Regards,
Vasishta
Comment 24 errata-xmlrpc 2017-09-05 16:49:52 EDT 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2640
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.