Login
Log in using an SSO provider:
Fedora Account System
Red Hat Associate
Login using a Red Hat Bugzilla account
Forgot Password
Create an Account
Red Hat Bugzilla – Bug 1842456
Home
New
Search
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh94 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
[?]
This site requires JavaScript to be enabled to function correctly, please enable it.
Bug 1842456
-
[Docs] W/A of
bz #1840539
to be added to the node replacement procedure
Summary:
[Docs] W/A of bz #1840539 to be added to the node replacement procedure
Keywords
:
Status
:
CLOSED CURRENTRELEASE
Alias:
None
Product:
Red Hat OpenShift Container Storage
Classification:
Red Hat Storage
Component:
documentation
Sub Component:
---
Version:
4.4
Hardware:
Unspecified
OS:
Unspecified
Priority:
unspecified
Severity:
unspecified
Target Milestone:
---
Target Release
:
OCS 4.4.0
Assignee:
Erin Donnelly
QA Contact:
Pratik Surve
Docs Contact:
URL:
Whiteboard:
Depends On:
1840539
1848455
Blocks:
1826040
1826482
1859307
TreeView+
depends on
/
blocked
Reported:
2020-06-01 09:56 UTC by
Pratik Surve
Modified:
2020-08-10 19:56 UTC (
History
)
CC List:
8 users
(
show
)
asriram
bkunal
ebenahar
jarrpa
madam
nberry
ocs-bugs
tnielsen
Fixed In Version:
Doc Type:
Bug Fix
Doc Text:
.Node replacement no longer leads to `Ceph HEALTH_WARN` state Previously, after node replacement, the Ceph CRUSH map tree still contained the stale hostname entry of the removed node in the particular rack. While replacing a node in a different rack, if any node with the same old hostname was added back to the cluster, it received a new rack label from the `ocs-operator`, but was inserted into its old place in the CRUSH map, resulting in an indefinite `Ceph HEALTH_WARN` state. With this release, this bug has been fixed and node replacement behaves as expected.
Clone Of:
Environment:
Last Closed:
2020-06-10 10:02:25 UTC
Embargoed:
Dependent Products:
Container Native Virtualization (CNV)
Kubernetes-native Infrastructure
Attachments
(Terms of Use)
Comment 10
Travis Nielsen
2020-06-02 16:46:54 UTC
Agreed with the approach, thanks.
Note
You need to
log in
before you can comment on or make changes to this bug.