Bug 1363689
Summary: | [RGW] After a cluster reboot, a rgw service restart is needed on the clients | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Tejas <tchandra> |
Component: | RGW | Assignee: | Matt Benjamin (redhat) <mbenjamin> |
Status: | CLOSED ERRATA | QA Contact: | shilpa <smanjara> |
Severity: | medium | Docs Contact: | Bara Ancincova <bancinco> |
Priority: | unspecified | ||
Version: | 2.0 | CC: | cbodley, ceph-eng-bugs, hnallurv, icolle, kbader, kdreyer, mbenjamin, owasserm, sweil |
Target Milestone: | rc | ||
Target Release: | 2.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | RHEL: ceph-10.2.5-14.el7cp Ubuntu: ceph_10.2.5-7redhat1xenial | Doc Type: | Bug Fix |
Doc Text: |
.Restart of the `radosgw` service on clients is no longer needed after rebooting the cluster
Previously, after rebooting the Ceph cluster, it was necessary to restart the `radosgw` service on the Ceph Object Gateway clients to restore the connection with the cluster. With this update, the restart of `radosgw` is no longer needed.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-03-14 15:44:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1322504, 1383917, 1412948 |
Description
Tejas
2016-08-03 11:05:04 UTC
We'd like more information on the amount of delay required before the secondary/primary radosgw process can be successfully restarted. Matt, who can provide that information? (In reply to Ken Dreyer (Red Hat) from comment #6) > Matt, who can provide that information? I don't recall the need for this info--I'll coordinate w/Shilpa Monday. Verified on ceph-10.2.5-27 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://rhn.redhat.com/errata/RHBA-2017-0514.html |