Created attachment 1259352 [details] wrong entry point Description of problem: Version-Release number of selected component (if applicable): 5.8.0.2-nightly.20170228141623_8710eed How reproducible: Steps to Reproduce: 1. Create a catalog item for ansible tower. 2. The default provisioning entry point is wrong .(The entry point does not exist in ManageIQ domain) 3. Save catalog item . validation message to correct the entry point is displayed. Actual results: Expected results: Additional info:
Tina - Is this just missing an automate domain update?
Greg, Yes, it is missing the Automate domain update, but the instance name(provision_from_bundle) should be changed as well. It will work with the current instance name because the .missing instance would be selected. I'll make a PR for the name change now. Thanks, Tina
https://github.com/ManageIQ/manageiq/pull/14168
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/0fdbe50ac3c01bbc176c1fccedb2e95d9245bec4 commit 0fdbe50ac3c01bbc176c1fccedb2e95d9245bec4 Author: Tina Fitzgerald <tfitzger> AuthorDate: Fri Mar 3 13:05:51 2017 -0500 Commit: Tina Fitzgerald <tfitzger> CommitDate: Fri Mar 3 13:05:51 2017 -0500 Fixed entry point instance name. https://bugzilla.redhat.com/show_bug.cgi?id=1428602 app/models/service_template_ansible_tower.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
*** Bug 1429857 has been marked as a duplicate of this bug. ***
Fixed in 5.8.0.4.20170307183144_745a3d9
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:1367