Red Hat Bugzilla – Bug 1460356
Ansible Service Catalog Template Job not honoring provider zone
Last modified: 2017-08-02 13:29:29 EDT
New commit detected on ManageIQ/manageiq/fine:
Author: Greg McCullough <firstname.lastname@example.org>
AuthorDate: Wed May 31 15:46:47 2017 -0400
Commit: Satoe Imaishi <email@example.com>
CommitDate: Fri Jun 9 16:12:04 2017 -0400
Merge pull request #15233 from tinaafitz/ansible_tower_my_zone
Add my_zone to ansible tower service template.
(cherry picked from commit e871897e55349892d83a4f52bc8b21d499e3dac6)
app/models/service_template_ansible_tower.rb | 4 ++++
spec/models/service_template_ansible_tower_spec.rb | 19 +++++++++++++++++++
2 files changed, 23 insertions(+)
The fix for this issue is for Ansible Tower, not Embedded Ansible, so it should be easier to test.
1. Setup 2 appliances, each having their own zone, zone1 and zone2.
2. Add Ansible Tower provider to zone2,
3. Create Ansible Tower Service item.
4. Order the Service. The work will be put on the queue for zone2 and the Service provision will complete successfully.
5. Stop the appliance for zone2.
6. Order the Service. The Service will not be provisioned.
7. Check the evm.log for a message showing the work being put on the queue, but never taken off. (Search for zone2 from the bottom, searching backwards)
Message will have this: "MIQ(MiqQueue.put) Message id" and a reference to zone2.
Let me know if you have any questions.
Can I access your environment?
I cant access either appliance.
Can you check it out?
Thanks for the update. That's great news.
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.