Bug 1730968 - [RFE] Satellite-clone should keep the same version of satellite from where it is being restored/cloned.
Summary: [RFE] Satellite-clone should keep the same version of satellite from where it...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Satellite Clone
Version: 6.5.0
Hardware: All
OS: All
urgent
urgent vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-18 04:44 UTC by Rajan Gupta
Modified: 2019-09-05 09:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-05 09:36:39 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Rajan Gupta 2019-07-18 04:44:00 UTC 
Description of problem:

[RFE] Satellite-clone should keep the same version of satellite from where it is being restored/cloned.

For eg.
Cloning Red Hat Satellite 6.4.1 to new destination server updating the version to 6.4.3 and it is failing during the satellite-clone process where as cloning it from 6.4.3 works fine and completed successfully.

Version-Release number of selected component (if applicable):
- Satellite 6.x

Steps to Reproduce:
1. Backup the source server using satellite-backup utility.
2. Copy and restore it to the destination server using satellite-clone utility.

Actual results:
Cloning the satellite server is updating the satellite version to the latest available minor version.

Expected results:
It should keep the same version of satellite from where it is being restored/cloned.
Comment 8 Rich Jerrido 2019-09-05 09:36:39 UTC 
If it is expected to retain the same z-stream version of the Satellite after a clone, use a Satellite ISO and set the 'enable_repos' option to false with Satellite-clone. There is no ability to 'install a specific z-stream version of Satellite from the CDN'
Note You need to log in before you can comment on or make changes to this bug.