Bug #23891
closedCommunity Job Templates are not assigned to all orgs by default
Description
The problem is, we don't put seeded templates under any org/loc. Core does it for provisioning and ptables.
Description of problem:
When I try to run "Run ansible roles" for apply assigned roles, I get this error message
"ERF42-5962 [Foreman::Exception]: No template mapped to feature Ansible: Run host roles"
Version-Release number of selected component (if applicable):
ansible-2.5.2-1.el7ae.noarch
tfm-rubygem-foreman_ansible-2.1.2.0.1-1.el7sat.noarch
tfm-rubygem-foreman_ansible_core-2.0.2-1.el7sat.noarch
rubygem-smart_proxy_ansible-2.0.2-3.el7sat.noarch
ansiblerole-insights-client-1.5-1.el7sat.noarch
The template has not been assigned to all organizations by default
How reproducible:
100%
Steps to Reproduce:
1. Import role to Sat6.4
2. Assign this role to host
3. Press button "Run ansible roles"
Actual results:
"ERF42-5962 [Foreman::Exception]: No template mapped to feature Ansible: Run host roles"
Expected results:
No error; the role will be apply to host
Updated by Marek Hulán over 6 years ago
- Copied from Bug #23742: Community Job Templates are not assigned to all orgs by default added
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/357 added
Updated by Anonymous over 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman_plugin|42f3cc3ca6f0c2a4c5e760e01458f94f35fe3ed1.
Updated by Stephen Benjamin over 6 years ago
- Related to Refactor #23939: Template "default" should cause templates to be seeded into all existing orgs and future ones added