Bug 1169299 - when creating DB dump, Satellite (except DB) should be stopped
Summary: when creating DB dump, Satellite (except DB) should be stopped
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Upgrades
Version: 570
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Jan Hutař
URL:
Whiteboard:
Depends On:
Blocks: sat570-upgrades
TreeView+ depends on / blocked
 
Reported: 2014-12-01 09:43 UTC by Jan Hutař
Modified: 2015-01-13 10:26 UTC (History)
0 users

Fixed In Version: rhn-upgrade-5.7.0.9-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-13 10:26:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Hutař 2014-12-01 09:43:37 UTC
Description of problem:
When creating DB dump, Satellite (except DB) should be stopped


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


How reproducible:
always


Steps to Reproduce:
1. In /etc/sysconfig/rhn/satellite-upgrade/doc/satellite-and-os-upgrade-postgresql.txt in step 1 you are supposed to create DB dump


Actual results:
1. Create database schema export for migration.

In this step, you will create an export of your current database schema, that
later in the process you will import into your newly built Satellite.

Run as root:

    cd /etc/sysconfig/rhn/satellite-upgrade/scripts
    ./spacewalk-dump-schema | \
        bzip2 -7c - | \
        split -d -b 2147483648 - /some/storage/path/schema-dump-

If you are upgrading from Satellite 5.6 run following command instead:

    db-control backup /some/storage/path/

Please have the schema dump files ready for import later in the process.


Expected results:
It should mention Satellite (except DB - on embedded variant) should be stopped

Comment 2 Jan Hutař 2014-12-01 11:20:53 UTC
Hmm, one more thing - IMO there should be similar warning (to stop Satellite) when you are restoring the dump on the target 5.7.0 Satellite. Currently there is:


4. Import database schema.

Database schema dump created previously in step one, will now be imported
into your Red Hat Satellite.

Run as root:

    (cat /path/to/schema-dump/files/schema-dump-* | \
    bzcat | \
    spacewalk-sql \
        --verbose \
        --select-mode-direct - && \
    echo "Schema import finished successfully") 2>&1 | tee /var/log/rhn/rhn-schema-import.log

If you are upgrading from Satellite 5.6 run following command instead:

    db-control restore /path/to/schema-dump/

Should the schema import fail, you will see error messages in your terminal
and the schema import log file.

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


Note You need to log in before you can comment on or make changes to this bug.