Bug 1175189

Summary:	various issues in database-migrations.txt document
Product:	Red Hat Satellite 5	Reporter:	Jan Hutař <jhutar>
Component:	Upgrades	Assignee:	Jan Dobes <jdobes>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	570	CC:	jdobes, lhellebr, tkasparek, tlestach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhn-upgrade-5.7.0.19-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-13 10:26:35 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:	1175398
Bug Blocks:	1128174

Description Jan Hutař 2014-12-17 10:08:59 UTC

Description of problem:
There are various issues with different importance levels in database-migrations.txt document. See the list below.


Version-Release number of selected component (if applicable):
rhn-upgrade-5.7.0.17-1.el6sat.noarch


How reproducible:
always


Steps to Reproduce:
1. Check /etc/sysconfig/rhn/satellite-upgrade/doc/database-migrations.txt


Actual results:
 * File (DB migration option) is not mentioned in README
 * There is "oracle-xe" mentioned multiple times, should be "oracle"
 * As the procedure is applicable for 5.6.0 and 5.7.0 only and these did not
   had embedded Oracle option, should we mention commands to manage Oracle
   at all? Usually we just say "Ask your DBA to do XYZ for you."
 * In rest of the documentation files in rhn-upgrade package, there are
   2 empty lines before each step beginning. This small fact makes
   orientation in documentation easier
 * Is `spacewalk-setup --db-only` correct step on Satellite installations?
   We do use only `install.pl` all the time in rest of the documentation.
 * Shouldn't we mention some DB requirements here?


Expected results:
See above

Comment 3 Lukáš Hellebrandt 2014-12-19 11:51:39 UTC

Verified.

Changes in '/etc/sysconfig/rhn/satellite-upgrade/doc/database-migrations.txt' and '/etc/sysconfig/rhn/satellite-upgrade/README' done according to the bugreport.

Comment 4 Clifford Perry 2015-01-13 10:26:35 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.