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.
Description of problem:
Currently, we do not have a way to prevent a user of Satellite 6 from filling up their partitions with database or pulp data, and we do not enforce explicit partitioning schemes to help prevent issues with bleed-over of over-syncing causing a user to fill up a partition which results in database corruption.
Proposal is to implement a a override-able warning into the installer that prevents initial run of the installer when items for postgres, mongo, and pulp are all found to be under the same partition with no division (i.e. /var).
Version-Release number of selected component (if applicable):
All
How reproducible:
100%
Steps to Reproduce:
1. You can install with any partition scheme.
2. You can fill up /var with data from pulp and corrupt your database content.
Actual results:
Caseload resulting from unknowingly breaking Satellite due to space issues
Expected results:
We should warn users of a best practice scenario and make them acknowledge that they are at risk for corrupting their data because of a non-divided partitioning scheme.
Additional info:
Related to RHBZ 1435420
Related side-note I've mentioned before, and will remind here: /var/lib/pulp and /var/cache/pulp should be on the same filesystem for single-machine deployments of Pulp, which of course includes Satellite. Having them on different filesystems will cause some tasks to take more time. We should make sure all Satellite deployments have them on the same filesystem.