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:
When you are running the Ansible Commands, it's creating the jobs but if anyone failed, then it will show '100% Failed'.
Version-Release number of selected component (if applicable):
6.12.1
How reproducible:
Create an Ansible Job with any server without communication or ssh key failure.
Steps to Reproduce:
1. Satellite WebUI
2. Monitor
3. Jobs
4. Run Job
5. Fill the Job information with two or more servers (host_collection or another way):
Job category *: Ansible Commands
Job template *: Run Command - Ansible Default
Search Query: host_collection=hc_test
Resolves to: 2 hosts
command *: id
Actual results:
Results: 100% Failed
Expected results:
Results: 50% Success - 50% Failed
Additional info:
- First test:
Job category *: Ansible Commands
Job template *: Run Command - Ansible Default
Search Query: host_collection=hc_test
Resolves to: 2 hosts
command *: id
Results: 100% Failed
Individual Result:
~~~ host 01 ~~~
35: PLAY RECAP *********************************************************************
36: host01.example.com : ok=3 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
37: Exit status: 4
~~~ end 01 ~~~
~~~ host 02 ~~~
16: PLAY RECAP *********************************************************************
17: host02.example.com : ok=0 changed=0 unreachable=1 failed=0 skipped=0 rescued=0 ignored=0
18: Exit status: 4
~~~ end 02 ~~~
- Second test:
Job category *: Commands
Job template *: Run Command - Script Default
Search Query: host_collection=hc_test
Resolves to: 2 hosts
command *: id
Results: 50% Success - 50% Failed
Individual Result:
~~~ host 01 ~~~
1: uid=0(root) gid=0(root) groups=0(root) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
2: Exit status: 0
~~~ end 01 ~~~
~~~ host 02 ~~~
1: Error initializing command: RuntimeError - Failed to establish connection to remote host, exit code: 255
2: Exit status: EXCEPTION
~~~ end 02 ~~~
Most likely a duplicate of BZ #2167396. I'll go ahead and close this one, if you feel this is actually not a duplicate, feel free to reopen.
*** This bug has been marked as a duplicate of bug 2167396 ***