Description of problem: When I'm performing 5.4.1@embeddedOracle@RHEL5 to 5.7.0@embeddedPostgeSQL@RHEL6, satellite-upgrade-estimates tool shows one step from satellite-and-os-upgrade-oracle.txt (although I have told it I'm going to migrate from Oracle to PostgreSQL) Version-Release number of selected component (if applicable): rhn-upgrade-5.7.0.13-1.el5sat How reproducible: always Steps to Reproduce: 1. On 5.4.1@embeddedOracle@RHEL5 run satellite-upgrade-estimates tool and answer "Y" for its only question Actual results: # /etc/sysconfig/rhn/satellite-upgrade/scripts/satellite-upgrade-estimates Will you be migrating your Red Hat Satellite database from Oracle to PostgreSQL? [N] Y Computing ... * Approximate disk space size required for PostgreSQL database: 10 - 14 GB * Approximate free space in Oracle data tablespace required for data migration: 0.46 GB satellite-and-os-upgrade-postgresql.txt, point 1: * Creating database schema export should take approximately 01:00 (HH:MM) satellite-and-os-upgrade-postgresql.txt, point 3: * OS and Red Hat Satellite installation should take approximately: 02:00 (HH:MM) satellite-and-os-upgrade-postgresql.txt, point 4: * Import of Red Hat Satellite schema should take approximately: 01:00 (HH:MM) satellite-and-os-upgrade-oracle.txt, point 4: * Upgrade of Red Hat Satellite database should take at least: 01:00 (HH:MM) * Minimum size of temporary tablespace required for schema upgrade is: 1156 MB Expected results: Estimate about "satellite-and-os-upgrade-oracle.txt, point 4" IMO should not be there
With the release of Red Hat Satellite 5.7 on January 12th 2015 this bug is being moved to a Closed Current Release state. The Satellite 5.7 GA Errata: - https://rhn.redhat.com/errata/RHSA-2015-0033.html Satellite 5.7 Release Notes: - https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html-single/Release_Notes/index.html Satellite Customer Portal Blog announcement for release: - https://access.redhat.com/blogs/1169563/posts/1315743 Cliff NOTE: This bug has not been re-verified (moved to RELEASE_PENDING) prior to release. We assume that the bug has indeed been fixed and not regressed since we initially verified it. Please re-open in the future if needed.