Project

General

Profile

Actions

Bug #11322

closed

Operating System created for Satellite server does not have partition table or templates assigned

Added by Brad Buckingham almost 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Hosts
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1251041
Description of problem:

It appears that when the Satellite server checks in via Puppet, an Operating System is created. That operating system does not have any partition table or templates assigned to it; therefore, that operating system cannot be used 'as is' for provisioning hosts. This causes issues for users (such as RHCI) which assume that the OS is correctly configured for use.

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

Satellite 6.1.1 SNAP15 builds:

foreman-proxy-1.7.2.5-1.el7sat.noarch
foreman-1.7.2.33-1.el7sat.noarch

How reproducible:

always

Steps to Reproduce:
1. install Satellite on a RHEL 7.1 server
2. go to Hosts -> Operating systems
3. select the Redhat 7.1 OS

Actual results:
Observe that no Partition table or Templates are assigned

Expected results:
Partition table and Templates should be assigned

Additional info:

Katello has an 'after_create' filter on the redhat model (in models/katello/concerns/redhat_extentions.rb) that should get triggered to do these associations; however, that does not appear to be getting triggered by the current process for the Satellite server. It does, however, get invoked when the server creates an OS as part of syncing a kickstart repository.

Actions

Also available in: Atom PDF