Bug 1443103
Summary: | [Scale Testing] Scaling of gluster volumes beyond 300 failed as the PVC's got stuck in Pending state indefinitely | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Prasanth <pprakash> |
Component: | heketi | Assignee: | Humble Chirammal <hchiramm> |
Status: | CLOSED ERRATA | QA Contact: | Prasanth <pprakash> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | cns-3.5 | CC: | hchiramm, kramdoss, mliyazud, pprakash, rcyriac, rhs-bugs, rreddy, storage-qa-internal, vinug |
Target Milestone: | --- | ||
Target Release: | CNS 3.6 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: |
This is a build, docker image related issue.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-10-11 07:07:22 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: | 1427156, 1451471, 1451474 | ||
Bug Blocks: | 1445447 |
Description
Prasanth
2017-04-18 13:16:10 UTC
This was due to a docker bug which should be fixed with latest docker. I am moving this bug to ON_QA. This bug shall be picked once we have a fix or workaround for https://bugzilla.redhat.com/show_bug.cgi?id=1473172 (In reply to krishnaram Karthick from comment #3) > This bug shall be picked once we have a fix or workaround for > https://bugzilla.redhat.com/show_bug.cgi?id=1473172 Karthick, if you have more than one device in your node, you could give a try :). Atleast it gives some confirmation about the scale part of it. 300 PVCs got created without any issues. There was no hangs, but there was some delay to create PVCs as the number of PVCs increased. 300th PVC took close to 4 minutes. Moving the bug to verified. 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/RHEA-2017:2879 |