Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1205731 - New provisioning templates not being associated to default organization by default
New provisioning templates not being associated to default organization by de...
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Provisioning (Show other bugs)
6.1.0
Unspecified Unspecified
unspecified Severity high (vote)
: Beta
: Unused
Assigned To: Stephen Benjamin
Og Maciel
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-03-25 10:34 EDT by Og Maciel
Modified: 2017-02-23 15:14 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-12 01:30:35 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1592 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 05:04:35 EDT

  None (edit)
Description Og Maciel 2015-03-25 10:34:54 EDT
Description of problem:

With the build from Satellite-6.1.0-RHEL-7-20150320.1 we now have two new provisioning templates:

* PXELinux default local boot
* kickstart_networking_setup

These need to be associated to the default organization during the installation or provisioning will fail with errors like:

* There was an error rendering the Katello Kickstart Default template: The specified snippet 'kickstart_networking_setup' does not exist, or is not a snippet.

Version-Release number of selected component (if applicable):

* Satellite-6.1.0-RHEL-7-20150320.1

How reproducible:


Steps to Reproduce:
1. Provision a new host using the Default Organization (build: Satellite-6.1.0-RHEL-7-20150320.1)
2.
3.

Actual results:

The boot process hangs

Expected results:


Additional info:

588:2015-03-25 07:44:15 [W] Failed to generate PXELinux template: undefined method `encoding' for nil:NilClass
593:2015-03-25 07:44:15 [I] Failed to save: Failed to generate PXELinux template: undefined method `encoding' for nil:NilClass
635:2015-03-25 07:45:37 [W] Failed to generate PXELinux template: undefined method `encoding' for nil:NilClass
640:2015-03-25 07:45:37 [I] Failed to save: Failed to generate PXELinux template: undefined method `encoding' for nil:NilClass
Comment 6 Og Maciel 2015-04-01 16:55:28 EDT
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
Comment 7 Bryan Kearney 2015-08-11 09:36:42 EDT
This bug is slated to be released with Satellite 6.1.
Comment 8 errata-xmlrpc 2015-08-12 01:30:35 EDT
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

Note You need to log in before you can comment on or make changes to this bug.