Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1624433

Summary: satellite-clone does not work on 6.4
Product: Red Hat Satellite Reporter: Ales Dujicek <adujicek>
Component: Satellite CloneAssignee: John Mitsch <jomitsch>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: adujicek, inecas
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-20 13:15:19 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:

Description Ales Dujicek 2018-08-31 14:46:19 UTC
Description of problem:

satellite-clone fails on 6.4

# satellite-clone
...

TASK [satellite-clone : Check for satellite version in metadata file] **********
Friday 31 August 2018  10:58:55 +0200 (0:00:00.022)       0:00:05.434 ********* 
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Satellite version is not supported or found. Only Satellite 6.2, 6.3 is supported."}
...
PLAY RECAP *********************************************************************
localhost                  : ok=27   changed=2    unreachable=0    failed=1   


I altered the code to skip that check to get further, and later there were more errors:

TASK [satellite-clone : change owner of backup directory to postgres] **********
Friday 31 August 2018  11:19:55 +0200 (0:15:55.757)       0:16:09.139 ********* 
fatal: [localhost]: FAILED! => {"changed": false, "gid": 0, "group": "root", "mode": "0770", "msg": "chown failed: failed to look up user postgres", "owner": "root", "path": "/tmp/satellite-backup-2018-08-31-07-58-41", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 152, "state": "directory", "uid": 0}

postgresql-server is be installed later by satellite-installer, see https://projects.theforeman.org/issues/23103
that is why there is not postgres user


TASK [satellite-clone : Start mongod] ******************************************
Friday 31 August 2018  16:04:11 +0200 (0:00:00.015)       0:17:09.055 ********* 
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Could not find the requested service mongod: host"}

in Sat 6.4 there is mongo 3.4 (different service name)


Version-Release number of selected component (if applicable):
satellite-clone-1.2.4-1.el7sat.noarch

Comment 2 John Mitsch 2018-08-31 17:50:33 UTC
Is there an expectation that 6.4 is supported? Satellite clone is primarily used for upgrades so it only supports 6.3 and under currently as the error message says

Comment 4 Ivan Necas 2018-09-03 08:32:46 UTC
I think we should target supporting 6.4 as well from the day one: the reason is the ability to spin up an independent environment, which can be used for other than upgrade purposes.

Comment 6 John Mitsch 2018-09-04 14:14:50 UTC
> I believe it should be supported. It is still described in documentation
https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_satellite/6.4-beta/html-single/upgrading_and_updating_red_hat_satellite/#sec-Cloning_to_Target

This is in the upgrade section so it's meant for a 6.3 machine. If it is not clear that this is meant to be done pre-upgrade to 6.4, please file a docs bug.

Comment 7 Ales Dujicek 2018-12-20 13:15:19 UTC

*** This bug has been marked as a duplicate of bug 1644152 ***