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.

Bug 2025212

Summary: during the "upgrade check" process, foreman-maintain should be able to stop/alert the user in case there isn't enough space to proceed with the pulp migration (v2 -> v3)
Product: Red Hat Satellite Reporter: Waldirio M Pinheiro <wpinheir>
Component: Satellite MaintainAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.9.0CC: ahumbe, apatel, iballou, kgaikwad
Target Milestone: UnspecifiedKeywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-17 14:09:32 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 Waldirio M Pinheiro 2021-11-20 18:38:52 UTC
Description of problem:
Once proceeding with the upgrade, there isn't enough space to proceed with the pulp migration. However, the *upgrade check* didn't mention it, causing an issue once the customer proceeded with the upgrade steps.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. don't keep enough space under /var/lib/pulp
2. execute foreman-maintain upgrade check
3.

Actual results:
It will pass with no reference about the required storage to migrate from pulp2 to pulp3

Expected results:
Stop the upgrade process and let the customer aware about it.

Additional info:

Comment 2 Ian Ballou 2023-07-17 14:09:32 UTC
Closing out this issue Satellite 6.9 is EOL and it's not blocking upgrades. Calculating disk usage for the upgrade would be a substantial RFE rather than a bug fix.