Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1167985

Summary: satellite-upgrade-estimates gives advices about Oracle when I'm on PostgreSQL and plans to stay that way
Product: Red Hat Satellite 5 Reporter: Jan Hutař <jhutar>
Component: UpgradesAssignee: Stephen Herr <sherr>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Hutař <jhutar>
Severity: medium Docs Contact:
Priority: high    
Version: 570CC: cperry
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhn-upgrade-5.7.0.12-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-13 10:25: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: 1128174    

Description Jan Hutař 2014-11-25 19:28:14 UTC
Description of problem:
Utility satellite-upgrade-estimates gives questions about Oracle when I'm on PostgreSQL and plan to stay that way (and migration PostgreSQL -> Oracle is not supported path)


Version-Release number of selected component (if applicable):
rhn-upgrade-5.7.0.6-1.el5sat


How reproducible:
always


Steps to Reproduce:
1. Have Satellite 5.6.0 with embedded PostgreSQL DB
2. # /etc/sysconfig/rhn/satellite-upgrade/scripts/satellite-upgrade-estimates


Actual results:
# /etc/sysconfig/rhn/satellite-upgrade/scripts/satellite-upgrade-estimates
Will you be upgrading both the operating system and Red Hat Satellite? [N] Y
Will you be migrating your Red Hat Satellite database from Oracle to PostgreSQL? [N] N

Computing ...


satellite-and-os-upgrade-oracle.txt, point 3:
* OS and Red Hat Satellite installation should take approximately: 02:00 (HH:MM)

satellite-and-os-upgrade-oracle.txt, point 4:
* Upgrade of Red Hat Satellite database should take approximately: 00:00 (HH:MM)

* Minimum size of temporary tablespace required for schema upgrade is: 1000 MB


1. It says DB upgrade will take 0 minutes (I doubt as I have DB with
   621 systems and 314 channels)
2. It says 1000 MB of temporary tablespace will be needed, but that
   sounds more like Oracle terminology to me
3. Computation itself is very slow


Expected results:
Should be quicker (took 6 minutes, 25 seconds on 4GB RAM and 2 CPUs system with Satellite turned off and only PostgreSQL service running) and should give more relevant results linked with correct points in correct files.

Comment 4 Clifford Perry 2015-01-13 10:25:53 UTC
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.