Bug #17103
closed
Provisioning templates are not usable for location when: "All provisioning templates" is checked for that location.
Added by Marek Hulán about 8 years ago.
Updated over 6 years ago.
Category:
Organizations and Locations
|
|
Description
Reporting on behalf of Petr Balogh
I am facing the issue when I use locations and have enabled: "All provisioning templates" for that location.
Seems that it doesn't work at all.
Work around which solved my problem is uncheck this checkbox and assign all provision templates for this location.
Foreman version is: 1.12.4
Related issues
1 (1 open — 0 closed)
- Assignee changed from Marek Hulán to Oded Ramraz
To reproduce:
- create a non-admin user in org A
- make org A ignoring provisioning templates - in it's form go to provisioning templates and check "All provisioning templates"
- create OS with PXELinux template correctly associated, verify you can save a host with such OS under admin account
- make sure that this PXELinux template is not associated to any organization
- login as that user, go to host edit form, change OS to the one you've prepared, you will see "No PXELinux templates were found for this host, make sure you define at least one in your $os settings or change PXE loader"
The reason is that we do @host.update in Taxonomy.no_taxonomy_scope block but ignoring only works for correctly set Organization.current. Same applies for locations. Host#provisioning_template should respect host's taxonomies.
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3972 added
- Target version set to 1.4.2
- Assignee changed from Oded Ramraz to Marek Hulán
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 189
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Anonymous