Bug 571564 - [RFE] Have reprovisioning tab default to original kickstart profile
Summary: [RFE] Have reprovisioning tab default to original kickstart profile
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.0.4
Hardware: All
OS: Linux
low
low
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: sat-nextgen
TreeView+ depends on / blocked
 
Reported: 2010-03-08 20:50 UTC by Issue Tracker
Modified: 2019-09-26 13:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 571566 (view as bug list)
Environment:
Last Closed: 2014-09-11 12:23:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Issue Tracker 2010-03-08 20:50:51 UTC
Escalated to Bugzilla from IssueTracker

Comment 1 Issue Tracker 2010-03-08 20:50:52 UTC
Event posted on 02-23-2010 04:54am EST by RFE-tool

1) Customer Name:
Eidgenossische-Technische Hochschule Zuerich (ETHK)

2) Nature Of Problem:
On the reprovisioning tab kickstart profile in which the client originally
has kickstarted, is not preselected.

Also, if a Client has a static network setup, it is necessary to manually
switch the network connection type to Static within the advanced options.

3) Business Requirements Satisfied By Request:
This will help their customers to simplify the task of reprovisioning.

4) Functional Requirements That Are Not Presently Possible:
On the reprovisioning tab, it would be great to have the kickstart profile
in which the client originally has kickstarted, preselected.

Also, if a Client has a static network setup, it should not be necessary
to manually switch the network connection type to Static within the
advanced options. At least the current setup should be preselected.

5) What Will Success Look Like:
If the original kickstart profile is not preselected, a customer may
easily miss to select the correct profile which will lead to a
broken/wrong system.

If a system has been provisioned with static network settings in the
kickstart file, the 'Static' option should also be preselected within
the Advanced Options of the Reprovisioning section.

6) Desired Release Vehicle:
RHN Satellite

7) Request Meets The Rhel Inclusion Criteria:
Yes

8) Affected Packages:
RHN Satellite

9) Sales Sponsor:
.

10) Rh Business Opportunity With Customer:
Sales person is in the middle of negotiating a renewal contract for about
1.700
Academic systems.

11) Status And Risk To Contract If Not Satisfied:
Satellite 5.3 is an important part for the whole renewal. The business
opp is between 150 K (1 year) and 360K (3 years)

12) If this request is vendor specific, has the customer engaged the
partner as well?:
Not Applicable




RFE-tool assigned to issue for SEG - Feature Request.

This event sent from IssueTracker by jwest  [SEG - Feature Request]
 issue 550823

Comment 2 Jeremy West 2010-03-08 20:54:46 UTC
This RFE asked for two different changes to be implemented.  This bug is tracking the kickstart profile part.  I've cloned this bug over to Bug 571566 to track the network option additions.

Comment 7 Mike McCune 2013-10-24 15:53:49 UTC
Moving to Satellte 6 for evaluation when we implement this area of functionality

Comment 10 Dominic Cleal 2014-01-20 15:36:02 UTC
The closest equivalent to profiles in Satellite 6 (and Foreman) is a host group and the template resolution feature, which means that the kickstart template for a given host is determined based on a hierarchy of the default for the OS, the default for an env, default for a host group and finally for the host group and env pair.

Since a host retains its host group after provisioning, when it's then reprovisioned, the appropriate template will still be resolved using the same host group.

Moving to ON_QA as I believe the original request is satisfied - when rebuilding a host, it will continue to use the appropriate kickstart.

Comment 12 Bryan Kearney 2014-09-11 12:23:54 UTC
This was delivered with Satellite 6.0 which was released on 10 September 2014.


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