Bug 1523954 - [RFE] Need a progress bar for satellite-clone command
Summary: [RFE] Need a progress bar for satellite-clone command
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Clone
Version: 6.3.0
Hardware: All
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: John Mitsch
QA Contact: Katello QA List
URL:
Whiteboard:
: 1523993 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-09 12:06 UTC by Neha Samant
Modified: 2019-04-12 15:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-19 17:23:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0330 0 normal SHIPPED_LIVE Satellite Maintenance bug fix update 2018-02-19 22:22:51 UTC

Description Neha Samant 2017-12-09 12:06:55 UTC
Description of problem:
when running command satellite-clone, We are unable to identify if the task id running or hung or its paused


Version-Release number of selected component (if applicable):
satellite 6.2.12 to Satellite 6.3 upgrade

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
[root@vm199 ~]# satellite-clone 
This will initiate a satellite-clone playbook using /usr/share/satellite-clone/satellite-clone-playbook.yml. Do you want to proceed? [y/n]
Running /usr/share/satellite-clone/satellite-clone-playbook.yml, output will show after playbook run

[DEPRECATION WARNING]: The use of 'include' for tasks has been deprecated. Use 'import_tasks' for static inclusions or 'include_tasks' for dynamic inclusions. This feature will be removed in a future release. Deprecation warnings can be 
disabled by setting deprecation_warnings=False in ansible.cfg.
[DEPRECATION WARNING]: include is kept for backwards compatibility but usage is discouraged. The module documentation details page may explain more about this rationale.. This feature will be removed in a future release. Deprecation 
warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
 [WARNING]: Consider using unarchive module rather than running tar
 [WARNING]: Consider using yum module rather than running yum

Expected results:
[root@vm199 ~]# satellite-clone 
This will initiate a satellite-clone playbook using /usr/share/satellite-clone/satellite-clone-playbook.yml. Do you want to proceed? [y/n]
Running /usr/share/satellite-clone/satellite-clone-playbook.yml, output will show after playbook run

[DEPRECATION WARNING]: The use of 'include' for tasks has been deprecated. Use 'import_tasks' for static inclusions or 'include_tasks' for dynamic inclusions. This feature will be removed in a future release. Deprecation warnings can be 
disabled by setting deprecation_warnings=False in ansible.cfg.
[DEPRECATION WARNING]: include is kept for backwards compatibility but usage is discouraged. The module documentation details page may explain more about this rationale.. This feature will be removed in a future release. Deprecation 
warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
 [WARNING]: Consider using unarchive module rather than running tar
 [WARNING]: Consider using yum module rather than running yum

#### 10 % Completed ## -->> need a progress bar

Additional info:

Comment 1 John Mitsch 2017-12-11 15:10:13 UTC
The next release of satellite clone (1.2.0+) will have real time task output showing from the ansible playbook that is being run

Comment 2 John Mitsch 2017-12-11 15:11:11 UTC
*** Bug 1523993 has been marked as a duplicate of this bug. ***

Comment 3 John Mitsch 2017-12-18 14:48:39 UTC
Sat-clone now has real-time output

Comment 4 Peter Ondrejka 2017-12-19 11:35:54 UTC
Verified with Maintenance 6, satellite-clone output now makes clear what task is currently running.

Comment 5 sthirugn@redhat.com 2018-02-12 20:51:03 UTC
*** Bug 1523993 has been marked as a duplicate of this bug. ***

Comment 8 errata-xmlrpc 2018-02-19 17:23: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/RHBA-2018:0330


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