Bug 1451013
| Summary: | PVC has to be minimum 4 GB when created dynamically via storage class which uses EBS device type : io1 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Elvir Kuric <ekuric> |
| Component: | Management Console | Assignee: | Zac Herman <zherman> |
| Status: | CLOSED ERRATA | QA Contact: | XiaochuanWang <xiaocwan> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.5.1 | CC: | aos-bugs, eboyd, hasha, jforrest, jokerman, mmccomas, smunilla, zherman |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | https://github.com/openshift/origin-web-console/pull/1587 | ||
| Whiteboard: | aos-scalability-35 | ||
| Fixed In Version: | https://github.com/openshift/origin-web-console/pull/1587 | Doc Type: | Enhancement |
| Doc Text: |
Feature: Users can now look at the events for a PVC on the detail page
Reason: Some PVCs never bind to a PV leaving the user with no information from the web console of why it remains in the 'pending' state. Now, the user can at least view what the error or warning message may be from the console.
Result: Users will be able to discover the reason PVCs may not be properly binding from the console.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-10 05:24:06 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: | |||
|
Description
Elvir Kuric
2017-05-15 14:50:04 UTC
The storage layer is behaving properly here. There is a limit of 4GB for EBS volumes, so the provisioning fails and sets the error message on the PVC. The error is in the web UI which doesn't properly handle the failed provisioning. Moving from storage to website. Does anyone have a running instance on AWS that has this setup that I can connect to and use. Otherwise are there instructions on getting the console to work from an AWS instance. Thanks. 1. First, per Brad Childs, the backend is properly not binding due to the size requirement. This translates to the user as stuck in pending state with a warning in the event list on the PVC. 2. When a user creates the PVC, it is a valid claim and there are no errors that we in the console can or should show. 3. The only way for a user to know what is going on is to do a describe on the cmd line of the pvc. Solution: Add the event data from the describe of the PVC on the PVC detail page which is not a bug fix as much as it is a feature request. PR will be open shortly. PR 1587 has been open to address this issue. https://github.com/openshift/origin-web-console/pull/1587 Note that this issue is not a bug as much as a poor user experience. As such, the solution simply gives more information to the user. The PVC will still not bind in this situation since it is not of the required size, but at least a user can now see why it is not working. After configuring storage class and dynamic provisioning to use aws-ebs provisioner and io1 device type, and try to create PVC smaller than 4 GB, will show the events information section on the specific PVC detail page and still remains "Pending state". Version OpenShift Master: v3.6.86 Kubernetes Master: v1.6.1+5115d708d7 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:1716 |