Bug 1320074 - katello-restore failing with /usr/bin/katello-restore:30:in ``': No such file or directory - katello-installer (Errno::ENOENT)
Summary: katello-restore failing with /usr/bin/katello-restore:30:in ``': No such file...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Backup & Restore
Version: 6.2.0
Hardware: x86_64
OS: Linux
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Christine Fouant
QA Contact: Renzo Nuccitelli
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-22 09:34 UTC by Tazim Kolhar
Modified: 2019-09-26 16:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 17:03:44 UTC
Target Upstream Version:


Attachments (Terms of Use)
Attaching foreman-debug (514.43 KB, application/x-xz)
2016-03-22 09:34 UTC, Tazim Kolhar
no flags Details

Description Tazim Kolhar 2016-03-22 09:34:16 UTC
Created attachment 1138951 [details]
Attaching foreman-debug

Description of problem:
katello-restore failing with /usr/bin/katello-restore:30:in ``': No such file or directory - katello-installer (Errno::ENOENT)

Version-Release number of selected component (if applicable):
# rpm -qa | grep foreman
tfm-rubygem-foreman_gutterball-0.0.1-6.el7sat.noarch
ibm-x3550m3-09.lab.eng.brq.redhat.com-foreman-proxy-1.0-1.noarch
foreman-selinux-1.11.0-1.el7sat.noarch
tfm-rubygem-foreman_theme_satellite-0.1.2-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman-0.5.1.2-1.el7sat.noarch
tfm-rubygem-foreman_openscap-0.5.3.0-1.el7sat.noarch
ibm-x3550m3-09.lab.eng.brq.redhat.com-foreman-client-1.0-1.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.10-2.el7sat.noarch
foreman-compute-1.11.0.6-1.el7sat.noarch
tfm-rubygem-foreman_bootdisk-6.1.0-1.el7sat.noarch
foreman-gce-1.11.0.6-1.el7sat.noarch
foreman-postgresql-1.11.0.6-1.el7sat.noarch
foreman-proxy-1.11.0.1-1.el7sat.noarch
foreman-installer-1.11.0.0-1.el7sat.noarch
tfm-rubygem-foreman-tasks-0.7.14.1-1.el7sat.noarch
foreman-vmware-1.11.0.6-1.el7sat.noarch
foreman-debug-1.11.0.6-1.el7sat.noarch
tfm-rubygem-foreman_hooks-0.3.9-2.el7sat.noarch
foreman-discovery-image-3.0.5-3.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-4.el7sat.noarch
foreman-1.11.0.6-1.el7sat.noarch
foreman-ovirt-1.11.0.6-1.el7sat.noarch
foreman-libvirt-1.11.0.6-1.el7sat.noarch
tfm-rubygem-foreman_discovery-5.0.0.1-1.el7sat.noarch
foreman-installer-katello-3.0.0.3-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.3-5.el7sat.noarch
tfm-rubygem-foreman_docker-2.0.1-1.el7sat.noarch
tfm-rubygem-foreman-redhat_access-1.0.1-1.el7sat.noarch
ibm-x3550m3-09.lab.eng.brq.redhat.com-foreman-proxy-client-1.0-1.noarch
puppet-foreman_scap_client-0.3.3-10.el7sat.noarch
tfm-rubygem-foreman_remote_execution-0.3.0.1-1.el7sat.noarch


How reproducible:
everytime

Steps to Reproduce:
1. Install a clean Satellite v.6.1.1 on rhel 7.1
2. Backup data from any other Satellite v.6.1.1(rhel7.1) with # katello-backup
Resetting Katello
tar (child): config_files.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
/usr/bin/katello-restore:30:in ``': No such file or directory - katello-installer (Errno::ENOENT)
	from /usr/bin/katello-restore:30:in `restore'
	from /usr/bin/katello-restore:64:in `<main>'


Actual results:
katello-restore script fails

Expected results:
katello-restore script should work as expected

Additional info:

Comment 1 Brad Buckingham 2016-03-22 17:14:50 UTC
Tazim, can you please provide the exact commands executed in the scenario above?  We need a bit more detail to reproduce the test scenario.

Comment 2 Tazim Kolhar 2016-04-09 13:20:55 UTC
The steps:

1. Install Satellite6
2. # katello-backup /tmp/katello-backup
3. # katello-restore /tmp/katello-backup

Comment 6 Renzo Nuccitelli 2017-10-25 13:18:06 UTC
Backup and Restore worked on Satellite 6.3.0 snap 21. Moving this BZ to verified.

Comment 7 Bryan Kearney 2018-02-21 17:03:44 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0336


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