Bug 1205731
Summary: | New provisioning templates not being associated to default organization by default | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Og Maciel <omaciel> |
Component: | Provisioning | Assignee: | Stephen Benjamin <stbenjam> |
Status: | CLOSED ERRATA | QA Contact: | Og Maciel <omaciel> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1.0 | CC: | jmontleo, mmccune |
Target Milestone: | Unspecified | ||
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-12 05:30:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Og Maciel
2015-03-25 14:34:54 UTC
Verified via web ui that these templates are now associated by default to the default organization. Also verified it via hammer cli: hammer> template list --organization='Default Organization' ---|---------------------------------------|---------- ID | NAME | TYPE ---|---------------------------------------|---------- 44 | Boot disk iPXE - generic host | Bootdisk 43 | Boot disk iPXE - host | Bootdisk 48 | idm_register | snippet 22 | Kickstart default iPXE | iPXE 21 | Kickstart default PXELinux | PXELinux 39 | kickstart_networking_setup | snippet 40 | puppet.conf | snippet 2 | PXELinux default local boot | PXELinux 1 | PXELinux global default | PXELinux 45 | Satellite Kickstart Default | provision 47 | Satellite Kickstart Default Finish | finish 46 | Satellite Kickstart Default User Data | user_data 49 | subscription_manager_registration | snippet ---|---------------------------------------|---------- Build Satellite-6.1.0-RHEL-6-20150331.1 This bug is slated to be released with Satellite 6.1. 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-2015:1592 |