Bug 1460356
Summary: | Ansible Service Catalog Template Job not honoring provider zone | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
Component: | Automate | Assignee: | Tina Fitzgerald <tfitzger> |
Status: | CLOSED ERRATA | QA Contact: | Pavol Kotvan <pakotvan> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 5.7.0 | CC: | akarol, cpelland, gmccullo, jhardy, mkanoor, obarenbo, pakotvan, tfitzger |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.8.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.8.1.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1451473 | Environment: | |
Last Closed: | 2017-08-02 17:29:29 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | CFME Core | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1451473 | ||
Bug Blocks: |
Comment 2
CFME Bot
2017-06-09 20:16:06 UTC
Hi Pavol, 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. Thanks, Tina Hi Pavol, Can I access your environment? Thanks, Tina Hi Pavol, I cant access either appliance. Can you check it out? Thanks, Tina Hi Pavol, Thanks for the update. That's great news. Thanks, Tina 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-2017:1758 |