Bug 1341800
| Summary: | [RFE] Make fact that system is out of space more clear | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | James Olin Oden <joden> |
| Component: | Content Management | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | Katello QA List <katello-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.0 | Keywords: | FutureFeature |
| Target Milestone: | Unspecified | ||
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-04 19:14:53 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: | 1212602 | ||
Moving 6.2 bugs out to sat-backlog. Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you. Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you. |
Description of problem: Was using QCI 1.2 to deploy RHEV, and as it was syncing Satellite repos I got an error: Syncing content...A subtask failed When I clicked on the link provided it took me to the details tab and shows a list a subtasks, with more than half of them "paused". If I clicked "resume" nothing seemed to happen. When I looked in the logs tab, I found no errors. I then tried to click on "Content -> Sync Status, but when I did this I received a blank page with the following error: We're sorry, but something went wrong. If you are the application owner check the logs for more information I then proceeded to explore the logs under /var/log/foreman. Deep down in the deployments log tree I found the a candlepin log which had entries like: Couldn't acquire next trigger: ERROR: could not extend file "base/16387/17165": No space left on device I then ran "df -k" and found root was completely full. Version-Release number of selected component (if applicable): QCI 1.2 How reproducible: I suspect always. Steps to Reproduce: 1. Create a VM with only 100Gb of space 2. Try to deploy RHEV. Actual results: Web UI errors that gave little clue to the actual problem. Expected results: A Web UI error that explained that we had ran of disk space. The reason is that in general you want to display an error that gets the customer as close as possible to the actual problem. This will reduce frustration for the customer and get them solving the problem sooner rather than later.