Bug 2234357 - Restart all ceph daemons when Encryption Compression(any Network.Connections options) change
Summary: Restart all ceph daemons when Encryption Compression(any Network.Connections ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: rook
Version: 4.14
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.14.0
Assignee: Subham Rai
QA Contact: Parag Kamble
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-24 06:08 UTC by Malay Kumar parida
Modified: 2023-11-08 18:55 UTC (History)
5 users (show)

Fixed In Version: 4.14.0-128
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-08 18:54:25 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage rook pull 517 0 None open Bug 2234357: core: restart ceph daemons when network updated 2023-09-04 07:01:34 UTC
Github rook rook issues 12622 0 None open Restart all ceph daemons when Encryption Compression(any Network.Connections options) change 2023-08-24 06:08:05 UTC
Github rook rook pull 12791 0 None open core: restart ceph daemons when network updated 2023-08-29 15:24:34 UTC
Red Hat Product Errata RHSA-2023:6832 0 None None None 2023-11-08 18:55:03 UTC

Description Malay Kumar parida 2023-08-24 06:08:05 UTC
Encryption settings are set in client-osd traffic & osd-osd traffic. When the settings change for the new settings to take effect 2 things are required,

1. Remapping of an RBD block device or remounting of a CephFS filesystem with the appropriate ms_mode option.
2. Restart ceph daemons to pick up the new settings. In the encryption case, we want the entire cluster to move to a new setting -- including the manager, MDS daemons, etc as in-transit encryption is generally considered an all-or-nothing thing.

Compression settings take effect between osd-osd traffic. When the settings change for the new settings to take effect 1 thing is required.

1. Restart ceph daemons to pick up the new settings.

Requiremsgr2 if it is set we should disable the v1 6789 port & only have the 3300 port, or if it's not enabled we should have both ports available. So when this setting changes either from on to off or off to on

1. we need to restart ceph daemons like the ceph mons

In all three cases whenever any option changes we need a restart of ceph daemons. So that's a common goal.

Comment 4 Subham Rai 2023-08-29 15:24:35 UTC
Forgot to add the pr link, added now

Comment 9 Subham Rai 2023-09-27 02:33:19 UTC
already provided the info, removing needinfo on me

Comment 12 errata-xmlrpc 2023-11-08 18:54:25 UTC
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 (Important: Red Hat OpenShift Data Foundation 4.14.0 security, enhancement & bug fix update), 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/RHSA-2023:6832


Note You need to log in before you can comment on or make changes to this bug.