Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJames Olin Oden
2016-06-01 19:01:21 UTC
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.
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.