Bug 1565547
| Summary: | [RFE] make satellite-clone non-interactive | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Nikhil Kathole <nkathole> |
| Component: | Satellite Clone | Assignee: | John Mitsch <jomitsch> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavel Stehlik <pstehlik> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3.1 | CC: | bkearney, jomitsch, mmccune |
| Target Milestone: | Unspecified | Keywords: | FutureFeature |
| 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: | 2020-03-05 17:23:13 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: | |||
I believe this was addressed by https://github.com/RedHatSatellite/satellite-clone/pull/335 Can we switch it to ON_QA? yes, feel free to push through the QA workflow The current version of foreman_maintain includes this fix. The current version of foreman_maintain includes this fix. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Description of problem: Currently satellite-clone has no option to make it fully non-interacting. It always asks user # satellite-clone This will initiate satellite-clone. Do you want to proceed? (y/n): As a tester, it is difficult to fully automate unless there is no option to byepass this interaction. It is good if we have option such as -y -y, --assumeyes Automatically answer yes for all questions Version-Release number of selected component (if applicable): # rpm -q satellite-clone satellite-clone-1.2.2-1.el7sat.noarch How reproducible:always Steps to Reproduce: 1. # satellite-clone -h usage: satellite-clone [-h] [--start-at-task START_AT_TASK] [--step] [--list-tasks] [--flush-cache] optional arguments: -h, --help show this help message and exit --start-at-task START_AT_TASK Start at a specific task --step interactive: confirm each task before running --list-tasks list tasks that will be run in the playbook --flush-cache clear the fact cache and run playbook Expected results: # satellite-clone -y should answer/proceed without asking "This will initiate satellite-clone. Do you want to proceed?" Additional info: