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.
Description of problem:
satellite-clone is failing with error "Please update the variables in satellite-clone-vars.yml".
Version-Release number of selected component (if applicable):
satellite-clone-1.1.4-1.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
1.Follow https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/installation_guide/upgrading_satellite_server_and_capsule_server#migrating_a_satellite_server
2.on the target server made the required changes for backup_dir and keep register_to_portal setting commented
3. run the satellite-clone
Actual results:
satellite-clone was failing with the below error-
---------------------------------
TASK [satellite-clone : Check that mandatory variables are updated] ******************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Please update the variables in satellite-clone-vars.yml (after copying satellite-clone-vars.sample.yml)"}
msg: Please update the variables in satellite-clone-vars.yml (after copying satellite-clone-vars.sample.yml)
to retry, use: --limit @/usr/share/satellite-clone/satellite-clone-playbook.retry
---------------------------------
Once the register_to_portal un-commented and explicitly set to false, stallite-clone ran.
Expected results:
Error message should be guiding to the accurate failure reason.
Additional info:
[root@target-server ~]# ll /backup/katello-backup-2017-12-14/
total 43551712
-rw-r--r--. 1 root root 1140339 Dec 14 18:17 candlepin.dump
-rw-r--r--. 1 root root 1732864 Dec 14 18:17 config_files.tar.gz
-rw-r--r--. 1 root root 27062971 Dec 14 18:17 foreman.dump
-rw-r--r--. 1 root root 0 Dec 14 18:17 metadata
drwxr-xr-x. 1 root root 36 Dec 14 18:17 mongo_dump
-rw-r--r--. 1 root root 44567007232 Dec 14 18:27 pulp_data.tar
If you have register_to_portal commented out, you have to use an activation key and org (in the top of satellite-clone-vars.yml)
Do you have this filled in?
@John, thanks for responding. In this scenario activation key was not used.
IMHO it would be good if error message could convey the failure reason, that will be more helpful for end user.
Comment 6sthirugn@redhat.com
2018-01-15 20:20:46 UTC